From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Pip Cet <pipcet@protonmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>,
Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, eller.helmut@gmail.com
Subject: Re: MPS: User GC customizations
Date: Thu, 04 Jul 2024 20:43:40 +0200 [thread overview]
Message-ID: <m2tth5vvz7.fsf@pro2.fritz.box> (raw)
In-Reply-To: <YgfcWaWK63yghYTFeDmSeQD9P_xyvz1EXPiId4K2sBnu9rNRJtdtx45WbTCgC17z9yrpdHexcM8yzbeTxEFkl3I0i3zSG4TSk1yOmym396w=@protonmail.com> (Pip Cet's message of "Thu, 04 Jul 2024 18:32:12 +0000")
Pip Cet <pipcet@protonmail.com> writes:
> On Thursday, July 4th, 2024 at 18:26, Ihor Radchenko <yantar92@posteo.net> wrote:
>> Gerd Möllmann gerd.moellmann@gmail.com writes:
>>
>> > Pip mentioned scan functions, so let's say we set a flag in_scan while
>> > being in dflt_scan. MPS now calls dflt_scan, in the MPS thread, to do an
>> > increment of its work. While in dflt_scan we get SIGPROF and land in the
>> > signal handler in main thread, and the profiler sees in_scan == true.
>> >
>> > Q: do we count that as part of GC work that the profiler should report,
>> > although it happened in the MPS thread? I understood Ihor as saying that
>> > he doesn't want that.
>>
>>
>> I think that we should ideally have multiple flags like this:
>> 1. when arena is locked
>> 2. when our dflt_scan code is running
>> 3. when we query MPS synchronously (e.g. memory allocation)
>> 4. when Emacs thread is paused by MPS
>
> 5. when our dflt_scan code is running on the main thread
>
> I think that's what Gerd meant to suggest, anyway?
I don't know. I only wanted to contribute something because I appeared
to be confused. Or maybe were confusing me. Whatever. I'm not thinking
about profiling otherwise.
next prev parent reply other threads:[~2024-07-04 18:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 9:26 MPS: Crash when switching to buffer Ihor Radchenko
2024-07-01 12:04 ` Eli Zaretskii
2024-07-01 12:13 ` Ihor Radchenko
2024-07-01 12:46 ` Eli Zaretskii
2024-07-01 14:14 ` Pip Cet
2024-07-01 14:42 ` Gerd Möllmann
2024-07-02 0:22 ` Pip Cet
2024-07-02 4:04 ` Gerd Möllmann
2024-07-02 11:40 ` Ihor Radchenko
2024-07-04 10:31 ` Ihor Radchenko
2024-07-04 11:48 ` Gerd Möllmann
2024-07-04 12:02 ` MPS: User GC customizations (was: MPS: Crash when switching to buffer) Ihor Radchenko
2024-07-04 12:51 ` MPS: User GC customizations Gerd Möllmann
2024-07-04 13:20 ` Ihor Radchenko
2024-07-04 14:45 ` Gerd Möllmann
2024-07-04 15:12 ` Pip Cet
2024-07-04 16:07 ` Gerd Möllmann
2024-07-04 16:38 ` Ihor Radchenko
2024-07-04 17:02 ` Gerd Möllmann
2024-07-04 17:53 ` Eli Zaretskii
2024-07-04 18:18 ` Gerd Möllmann
2024-07-04 18:28 ` Ihor Radchenko
2024-07-04 18:32 ` Pip Cet
2024-07-04 18:43 ` Gerd Möllmann [this message]
2024-07-04 18:39 ` Eli Zaretskii
2024-07-04 18:48 ` Ihor Radchenko
2024-07-04 13:58 ` Eli Zaretskii
2024-07-04 14:30 ` Gerd Möllmann
2024-07-04 15:43 ` Eli Zaretskii
2024-07-04 15:48 ` Eli Zaretskii
2024-07-04 15:52 ` Pip Cet
2024-07-04 16:04 ` Eli Zaretskii
2024-07-04 17:01 ` Gerd Möllmann
2024-07-04 18:03 ` Eli Zaretskii
2024-07-04 18:28 ` Gerd Möllmann
2024-07-04 18:43 ` Eli Zaretskii
2024-07-04 19:09 ` Gerd Möllmann
2024-07-04 19:12 ` Eli Zaretskii
2024-07-04 16:38 ` Pip Cet
2024-07-04 17:06 ` Gerd Möllmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2tth5vvz7.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=pipcet@protonmail.com \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.