Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Stefan Monnier <monnier@iro.umontreal.ca>
Newsgroups: comp.arch
Subject: Re: MSI interrupts
Date: Thu, 27 Mar 2025 21:52:56 -0400
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <jwv7c49j540.fsf-monnier+comp.arch@gnu.org>
References: <vqto79$335c6$1@dont-email.me>
	<7a093bbb356e3bda3782c15ca27e98a7@www.novabbs.org>
	<vs41ap$n43$1@reader1.panix.com>
	<601781e2c91d42a73526562b419fdf02@www.novabbs.org>
	<vs4se6$hvb$1@reader1.panix.com>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Fri, 28 Mar 2025 02:52:57 +0100 (CET)
Injection-Info: dont-email.me; posting-host="292fdbf2d6f68c149d24f9a4ffafec08";
	logging-data="1676228"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19MFT39Cgcn0pItiNqG1o/rdih7LG0ZhuM="
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:8wjQYS2LdcN57HXG3xEQtK/k+dA=
	sha1:h9dltWWDmQOs1c+z3GzMMJAOfv4=

> Ok.  So let's be crystal clear here: after the event concludes
> successfully, a subsequent exception, interrupt, or whatever,
> will not magically roll back any of the values set and made
> visible system-wide as a result of the successful conclusion of
> the atomic event.  Correct?  That's what I've been asking.

I don't really understand how that can be a question.  It would
completely invalidate the notion of the chunk of code being executed
*atomically*.

If a value has been made visible system-wide, it's like sending an
email: you can't undo that.


        Stefan