All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Baptiste Le Duc <baptiste.le-duc@vates.tech>,
	xen-devel@lists.xenproject.org
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Julien Grall" <julien@xen.org>,
	"Roger Pau Monné" <roger@xenproject.org>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Connor Davis" <connojdavis@gmail.com>
Subject: Re: [PATCH v3 6/6] xen/riscv: make Zihintpause no longer a required extension
Date: Wed, 30 Sep 2026 12:43:18 +0200	[thread overview]
Message-ID: <08f1537c-f1c5-4839-99c2-e15e1729658f@gmail.com> (raw)
In-Reply-To: <1790699586.8631fc262581453bbf619ec5b2062170.1a0ee034479000b504@vates.tech>



On 9/29/26 6:32 PM, Baptiste Le Duc wrote:
> Zihintpause is in required_extensions[] so Xen panics when it is missing,
> while it does not strictly require hardware support for it.
> 
> The PAUSE hint (Zihintpause extension) is encoded as FENCE W, 0
> (0x0100000F). In accordance with the RISC-V Unprivileged ISA, HINTs are
> encoded in the space of valid standard instructions. On platforms without
> Zihintpause support, executing 0x0100000F is treated as a standard FENCE
> with an empty successor set, which acts as a NOP and never generates an
> illegal instruction trap.
> 
> Zihintpause is therefore purely an optimization hint. Drop it from
> required_extensions[] so Xen can still boot on systems that don't advertise
> it, and print a warning in that case.
> 
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Baptiste Le Duc <baptiste.le-duc@vates.tech>
> ---
> Changes since v2:
> - rewrite commit message
> - print a warning at boot when Zihintpause is unavailable
> - drop Zihintpause requirement from booting.txt
> ---
> Changes since v1:
> - rewrite commit message.
> ---
LGTM:

Reviewed-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>

Thanks.

~ Oleksii


      reply	other threads:[~2026-09-30 10:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 16:29 [PATCH v3 0/6] xen/riscv: fix boot on missing extensions and MMU setup bugs Baptiste Le Duc
2026-09-29 16:32 ` [PATCH v3 1/6] docs/riscv: sync required ISA extensions with required_extensions[] Baptiste Le Duc
2026-09-30  6:18   ` Jan Beulich
2026-09-30 10:32   ` Oleksii Kurochko
2026-09-29 16:32 ` [PATCH v3 2/6] xen/riscv: rename PTE "permissions" to "pte_flags" Baptiste Le Duc
2026-09-30 12:07   ` Jan Beulich
2026-09-30 12:42     ` Baptiste Le Duc
2026-09-30 12:50       ` Jan Beulich
2026-09-30 12:46     ` [PATCH v3.1 " Baptiste Le Duc
2026-09-30 12:51       ` Baptiste Le Duc
2026-09-30 13:34     ` [PATCH v3 " Oleksii Kurochko
2026-09-30 13:04   ` [PATCH RESEND " Anthony PERARD
2026-09-30 13:42   ` [PATCH " Oleksii Kurochko
2026-09-30 13:54     ` Jan Beulich
2026-09-30 13:56       ` Oleksii Kurochko
2026-10-01  7:41     ` Jan Beulich
2026-09-29 16:32 ` [PATCH v3 3/6] xen/riscv: fix A/D bit handling in G-stage mappings Baptiste Le Duc
2026-09-30 12:20   ` Jan Beulich
2026-09-30 13:53     ` Oleksii Kurochko
2026-09-30 13:58       ` Jan Beulich
2026-09-30 14:03         ` Oleksii Kurochko
2026-09-29 16:32 ` [PATCH v3 4/6] xen/riscv: fix A/D bits in Xen's page-table mappings Baptiste Le Duc
2026-09-30 12:23   ` Jan Beulich
2026-09-30 14:37   ` Oleksii Kurochko
2026-09-29 16:32 ` [PATCH v3 5/6] xen/riscv: use pte_is_valid() in pte_is_mapping() Baptiste Le Duc
2026-09-30 10:45   ` Oleksii Kurochko
2026-09-29 16:32 ` [PATCH v3 6/6] xen/riscv: make Zihintpause no longer a required extension Baptiste Le Duc
2026-09-30 10:43   ` Oleksii Kurochko [this message]

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=08f1537c-f1c5-4839-99c2-e15e1729658f@gmail.com \
    --to=oleksii.kurochko@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=baptiste.le-duc@vates.tech \
    --cc=connojdavis@gmail.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger@xenproject.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.