From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v4 1/2] kvm: add support for guest physical bits
Date: Wed, 20 Mar 2024 10:44:58 +0800 [thread overview]
Message-ID: <54e8b518-2bea-4a5b-a75a-4fd45535c6fa@intel.com> (raw)
In-Reply-To: <20240318155336.156197-2-kraxel@redhat.com>
On 3/18/2024 11:53 PM, Gerd Hoffmann wrote:
> Query kvm for supported guest physical address bits, in cpuid
> function 80000008, eax[23:16]. Usually this is identical to host
> physical address bits. With NPT or EPT being used this might be
> restricted to 48 (max 4-level paging address space size) even if
> the host cpu supports more physical address bits.
>
> When set pass this to the guest, using cpuid too. Guest firmware
> can use this to figure how big the usable guest physical address
> space is, so PCI bar mapping are actually reachable.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> target/i386/cpu.h | 1 +
> target/i386/cpu.c | 1 +
> target/i386/kvm/kvm-cpu.c | 31 ++++++++++++++++++++++++++++++-
> 3 files changed, 32 insertions(+), 1 deletion(-)
>
> diff --git a/target/i386/cpu.h b/target/i386/cpu.h
> index 952174bb6f52..d427218827f6 100644
> --- a/target/i386/cpu.h
> +++ b/target/i386/cpu.h
> @@ -2026,6 +2026,7 @@ struct ArchCPU {
>
> /* Number of physical address bits supported */
> uint32_t phys_bits;
> + uint32_t guest_phys_bits;
>
> /* in order to simplify APIC support, we leave this pointer to the
> user */
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index 9a210d8d9290..c88c895a5b3e 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -6570,6 +6570,7 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index, uint32_t count,
> if (env->features[FEAT_8000_0001_EDX] & CPUID_EXT2_LM) {
> /* 64 bit processor */
> *eax |= (cpu_x86_virtual_addr_width(env) << 8);
> + *eax |= (cpu->guest_phys_bits << 16);
> }
> *ebx = env->features[FEAT_8000_0008_EBX];
> if (cs->nr_cores * cs->nr_threads > 1) {
> diff --git a/target/i386/kvm/kvm-cpu.c b/target/i386/kvm/kvm-cpu.c
> index 9c791b7b0520..5132bb96abd5 100644
> --- a/target/i386/kvm/kvm-cpu.c
> +++ b/target/i386/kvm/kvm-cpu.c
> @@ -18,10 +18,33 @@
> #include "kvm_i386.h"
> #include "hw/core/accel-cpu.h"
>
> +static void kvm_set_guest_phys_bits(CPUState *cs)
> +{
> + X86CPU *cpu = X86_CPU(cs);
> + uint32_t eax, guest_phys_bits;
> +
> + eax = kvm_arch_get_supported_cpuid(cs->kvm_state, 0x80000008, 0, R_EAX);
> + guest_phys_bits = (eax >> 16) & 0xff;
> + if (!guest_phys_bits) {
> + return;
> + }
> +
> + if (cpu->guest_phys_bits == 0 ||
> + cpu->guest_phys_bits > guest_phys_bits) {
> + cpu->guest_phys_bits = guest_phys_bits;
> + }
> +
> + if (cpu->host_phys_bits_limit &&
> + cpu->guest_phys_bits > cpu->host_phys_bits_limit) {
> + cpu->guest_phys_bits = cpu->host_phys_bits_limit;
host_phys_bits_limit takes effect only when cpu->host_phys_bits is set.
If users pass configuration like "-cpu
qemu64,phys-bits=52,host-phys-bits-limit=45", the cpu->guest_phys_bits
will be set to 45. I think this is not what we want, though the usage
seems insane.
We can guard it as
if (cpu->host_phys_bits && cpu->host_phys_bits_limit &&
cpu->guest_phys_bits > cpu->host_phys_bits_limt)
{
}
Simpler, we can guard with cpu->phys_bits like below, because
cpu->host_phys_bits_limit is used to guard cpu->phys_bits in
host_cpu_realizefn()
if (cpu->guest_phys_bits > cpu->phys_bits) {
cpu->guest_phys_bits = cpu->phys_bits;
}
with this resolved,
Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
> + }
> +}
> +
> static bool kvm_cpu_realizefn(CPUState *cs, Error **errp)
> {
> X86CPU *cpu = X86_CPU(cs);
> CPUX86State *env = &cpu->env;
> + bool ret;
>
> /*
> * The realize order is important, since x86_cpu_realize() checks if
> @@ -50,7 +73,13 @@ static bool kvm_cpu_realizefn(CPUState *cs, Error **errp)
> MSR_IA32_UCODE_REV);
> }
> }
> - return host_cpu_realizefn(cs, errp);
> + ret = host_cpu_realizefn(cs, errp);
> + if (!ret) {
> + return ret;
> + }
> +
> + kvm_set_guest_phys_bits(cs);
> + return true;
> }
>
> static bool lmce_supported(void)
next prev parent reply other threads:[~2024-03-20 2:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 15:53 [PATCH v4 0/2] kvm: add support for guest physical bits Gerd Hoffmann
2024-03-18 15:53 ` [PATCH v4 1/2] " Gerd Hoffmann
2024-03-20 2:44 ` Xiaoyao Li [this message]
2024-03-22 12:50 ` Gerd Hoffmann
2024-03-27 8:53 ` Paolo Bonzini
2024-03-18 15:53 ` [PATCH v4 2/2] target/i386: add guest-phys-bits cpu property Gerd Hoffmann
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=54e8b518-2bea-4a5b-a75a-4fd45535c6fa@intel.com \
--to=xiaoyao.li@intel.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.lendacky@amd.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).