Path: ...!weretis.net!feeder9.news.weretis.net!panix!.POSTED.spitfire.i.gajendra.net!not-for-mail
From: cross@spitfire.i.gajendra.net (Dan Cross)
Newsgroups: comp.arch
Subject: Re: MSI interrupts
Date: Fri, 28 Mar 2025 02:58:29 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <vs538l$rd4$3@reader1.panix.com>
References: <vqto79$335c6$1@dont-email.me> <601781e2c91d42a73526562b419fdf02@www.novabbs.org> <vs4se6$hvb$1@reader1.panix.com> <jwv7c49j540.fsf-monnier+comp.arch@gnu.org>
Injection-Date: Fri, 28 Mar 2025 02:58:29 -0000 (UTC)
Injection-Info: reader1.panix.com; posting-host="spitfire.i.gajendra.net:166.84.136.80";
	logging-data="28068"; mail-complaints-to="abuse@panix.com"
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: cross@spitfire.i.gajendra.net (Dan Cross)
Bytes: 1823
Lines: 21

In article <jwv7c49j540.fsf-monnier+comp.arch@gnu.org>,
Stefan Monnier  <monnier@iro.umontreal.ca> wrote:
>> 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.

Yup, it sure would.  But when Mitch was talking about locks
disappearing, it wasn't clear (to me anyway) that he was talking
about something in the hardware, and not the mutexes I was
trying to build in software; hence why I was asking.

	- Dan C.