Re: MSI interrupts

In article <7b53bc22cfbacd27f9e735cc42ce908c@www.novabbs.org>,
MitchAlsup1 <mitchalsup@aol.com> wrote:

Somehow the post was pushed before being edited. There seems to be
some control sequence that finds and pushes the Post-button--this
in not the only web site this happens to me on.

Clearly it wasn't part of some ESM atomic event.

(Jokes aside, it happens.  No worries.)

On Fri, 28 Mar 2025 1:01:59 +0000, Dan Cross wrote:
>

In article <601781e2c91d42a73526562b419fdf02@www.novabbs.org>,
MitchAlsup1 <mitchalsup@aol.com> wrote:

-----------------------

>
The property that if an interrupt (or exception or SVC or SVR)
prevents executing the event to its conclusion, HW makes the
event look like it never started. So that when/if control returns
we have another chance to execute the event as-if ATOMICally.

>
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.

>
If the esmLOCKstore() retires, the participating memory becomes visible
at that instant and cannot be subsequently undone.

Ok.  That's what I was asking.

If the esmLOCKabandon( ) retires, participating memory reverts to its
pre-event state in that instant as if the event never happened.

- Dan C.