All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kunwu Chan <kunwu.chan@linux.dev>
To: perfbook@vger.kernel.org
Cc: paulmck@kernel.org, Kunwu Chan <kunwu.chan@linux.dev>
Subject: [PATCH] memorder: Realign OMCA visibility attribution with litmus causality
Date: Wed, 11 Mar 2026 17:29:35 +0800	[thread overview]
Message-ID: <20260311092935.983280-1-kunwu.chan@linux.dev> (raw)

Fix the OMCA explanatory text to attribute the two stores to P0 (not P1), matching C-MP-OMCA+o-o-o+o-rmb-o.litmus. This keeps the narrative causality aligned with the executable model.

Signed-off-by: Kunwu Chan <kunwu.chan@linux.dev>
---
 memorder/memorder.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index 8eb14a29..388903b6 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -2415,7 +2415,7 @@ value directly from the store buffer, which improves performance.
 
 	In contrast, on an other-multicopy-atomic platform, \co{P0()}
 	could see its own store early, so that there would be no constraint
-	on the order of visibility of the two stores from \co{P1()},
+	on the order of visibility of the two stores from \co{P0()},
 	which in turn allows the \co{exists} clause to trigger.
 }\QuickQuizEnd
 
-- 
2.25.1


                 reply	other threads:[~2026-03-11  9:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260311092935.983280-1-kunwu.chan@linux.dev \
    --to=kunwu.chan@linux.dev \
    --cc=paulmck@kernel.org \
    --cc=perfbook@vger.kernel.org \
    /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.
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.