Sujet : Re: MSI interrupts
De : chris.m.thomasson.1 (at) *nospam* gmail.com (Chris M. Thomasson)
Groupes : comp.archDate : 28. Mar 2025, 03:14:21
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vs50lt$1jq5h$4@dont-email.me>
References : 1 2 3 4 5 6 7
User-Agent : Mozilla Thunderbird
On 3/27/2025 7:02 PM, Stefan Monnier wrote:
If the esmLOCKstore() retires, the participating memory becomes visible
at that instant and cannot be subsequently undone.
>
If the esmLOCKabandon( ) retires, participating memory reverts to its
pre-event state in that instant as if the event never happened.
Thinking about Haskell's STM (Software Transactional Memory) library:
Oh shit. I have had some bad experiences with STM. Way back. Damn live lock scenarios, ect... Issues with LL/SC live lock wrt false sharing on the reservation granules, ect...
do you happen to offer an `esmLOCKretry` which would cause the event to
be aborted and started over? If you do, does it start over right away
or can it *wait* until a snoop request comes to invalidate one of the
participating lines?
[ This last functionality is how STM's `retry` works: it watches all
the memory locations that were consulted during the failed run, knowing
that as long as they're not modified it's pointless to run the
transaction again because it would fail in the same way. ]
MSI interrupts
Re: MSI interrupts