From: Marc Zyngier <maz@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, arnd@arndb.de,
kernel-team@meta.com, vincenzo.frascino@arm.com,
anders.roxell@linaro.org, ndecarli@meta.com, rmikey@meta.com
Subject: Re: [PATCH RFC] arm64: vdso: Use __arch_counter_get_cntvct()
Date: Thu, 03 Apr 2025 18:59:44 +0100 [thread overview]
Message-ID: <871pu9yvlb.wl-maz@kernel.org> (raw)
In-Reply-To: <Z+57uXX3u0zeTGeP@gmail.com>
On Thu, 03 Apr 2025 13:14:49 +0100,
Breno Leitao <leitao@debian.org> wrote:
>
> Since you created *all* this noise regarding instruction ordering, can
> I pick your brain in the same topic? :-P
>
> If my machine has Speculation Barrier (sb)[1] support, is it a good
> replacement for `isb` ? Do you happen to know?
Probably not. SB prevent speculation past it, while ISB is here to
enforce ordering. We're pretty happy to let the CPU speculate the
counter, as long as it does it the order we have defined.
On some implementation, this can be have a similar effect (drain the
fetch queue, restart). But the intent clearly isn't the same, and some
implementations may do things differently.
In any case, what you want is CNTVCTSS_EL0 (part of FEAT_ECV), which
does away with all barriers.
M.
--
Jazz isn't dead. It just smells funny.
next prev parent reply other threads:[~2025-04-03 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 19:22 [PATCH RFC] arm64: vdso: Use __arch_counter_get_cntvct() Breno Leitao
2025-04-02 22:04 ` Marc Zyngier
2025-04-02 22:22 ` Marc Zyngier
2025-04-03 12:14 ` Breno Leitao
2025-04-03 17:59 ` Marc Zyngier [this message]
2025-04-04 13:36 ` Breno Leitao
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=871pu9yvlb.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndecarli@meta.com \
--cc=rmikey@meta.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).