[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <vgqqpqfqin34stqyd2gdqxiopw6vornjpmomuyctx7ngbtjj5t@ly4avedudyrx>
Date: Thu, 5 Feb 2026 08:56:33 -0600
From: Andrew Jones <andrew.jones@....qualcomm.com>
To: fangyu.yu@...ux.alibaba.com
Cc: pbonzini@...hat.com, corbet@....net, anup@...infault.org,
atish.patra@...ux.dev, pjw@...nel.org, palmer@...belt.com,
aou@...s.berkeley.edu, alex@...ti.fr, guoren@...nel.org,
radim.krcmar@....qualcomm.com, linux-doc@...r.kernel.org,
kvm@...r.kernel.org, kvm-riscv@...ts.infradead.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 0/3] Support runtime configuration for per-VM's HGATP
mode
On Wed, Feb 04, 2026 at 09:45:04PM +0800, fangyu.yu@...ux.alibaba.com wrote:
> From: Fangyu Yu <fangyu.yu@...ux.alibaba.com>
>
> Currently, RISC-V KVM hardcodes the G-stage page table format (HGATP mode)
> to the maximum mode detected at boot time (e.g., SV57x4 if supported). but
> often such a wide GPA is unnecessary, just as a host sometimes doesn't need
> sv57.
>
> This patch introduces per-VM configurability of the G-stage mode via a new
> KVM capability: KVM_CAP_RISCV_SET_HGATP_MODE. User-space can now explicitly
> request a specific HGATP mode (SV39x4, SV48x4, SV57x4 or SV32x4) during
> VM creation.
>
For the series,
Reviewed-by: Andrew Jones <andrew.jones@....qualcomm.com>
Powered by blists - more mailing lists