all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Helmut Eller <eller.helmut@gmail.com>,
	Emacs Devel <emacs-devel@gnu.org>
Subject: Re: MPS: Bytecode stack
Date: Mon, 6 May 2024 15:54:43 +0200	[thread overview]
Message-ID: <8A6529B6-511F-4E61-9507-F204EDCF1B76@gmail.com> (raw)
In-Reply-To: <m2h6fbgj0z.fsf@pro2.fritz.box>

6 maj 2024 kl. 15.35 skrev Gerd Möllmann <gerd.moellmann@gmail.com>:

> Or, wait a moment... I'm wondering about what happens when the client
> continues to exec byte code while we are scanning... The root is not
> like objects in MPS memory to which we get granted exclusive access. Or
> so I think ATM. But roots can have a barrier applied to them, I think.
> MPS_RM_PROT. I have to read a bit.

Yes, that's basically what I was wondering and the reason for the synthetic little example.

Essentially, what context is the scanning code running in? The mutator thread? If so, as an async signal handler, or in a more controlled context? If in a separate thread, does the mutator keep running? How did we get hold of the mutator stack and registers? And so on.




  reply	other threads:[~2024-05-06 13:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  9:58 MPS: Bytecode stack Gerd Möllmann
2024-05-06 12:12 ` Mattias Engdegård
2024-05-06 12:47   ` Gerd Möllmann
2024-05-06 13:07     ` Mattias Engdegård
2024-05-06 13:23       ` Gerd Möllmann
2024-05-06 13:35         ` Gerd Möllmann
2024-05-06 13:54           ` Mattias Engdegård [this message]
2024-05-06 14:02             ` Gerd Möllmann
2024-05-06 14:14               ` Gerd Möllmann
2024-05-06 15:59               ` Mattias Engdegård

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=8A6529B6-511F-4E61-9507-F204EDCF1B76@gmail.com \
    --to=mattias.engdegard@gmail.com \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    /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.