From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page PR_RISCV_SET_ICACHE_FLUSH_CTX.2const
Date: Thu, 25 Dec 2025 22:06:56 +0100 [thread overview]
Message-ID: <aU2nZwzQd4XdB5GJ@devuan> (raw)
In-Reply-To: <aUv63u9zgsyD78QB@meinfjell.helgefjelltest.de>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
On Wed, Dec 24, 2025 at 02:38:22PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue: scope → I<scope>
Fixed; thanks!
>
> "When scope is set to B<PR_RISCV_SCOPE_PER_PROCESS> all threads in the "
> "process are permitted to emit icache flushing instructions. Whenever any "
> "thread in the process is migrated, the corresponding hart's icache will be "
> "guaranteed to be consistent with instruction storage. This does not enforce "
> "any guarantees outside of migration. If a thread modifies an instruction "
> "that another thread may attempt to execute, the other thread must still emit "
> "an icache flushing instruction before attempting to execute the potentially "
> "modified instruction. This must be performed by the user-space program."
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-25 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 14:38 Issue in man page PR_RISCV_SET_ICACHE_FLUSH_CTX.2const Helge Kreutzmann
2025-12-25 21:06 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-24 14:38 Helge Kreutzmann
2025-12-25 21:03 ` Alejandro Colomar
2025-12-24 14:38 Helge Kreutzmann
2025-12-24 14:38 Helge Kreutzmann
2025-12-25 13:59 ` Alejandro Colomar
2025-12-24 14:38 Helge Kreutzmann
2025-12-24 15:52 ` Alejandro Colomar
2025-12-24 14:38 Helge Kreutzmann
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=aU2nZwzQd4XdB5GJ@devuan \
--to=alx@kernel.org \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
/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).