qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yang Weijiang <weijiang.yang@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Yang Weijiang <weijiang.yang@intel.com>,
	qemu-devel@nongnu.org, seanjc@google.com
Subject: Re: [Qemu-devel][PATCH] x86/cpu: Use max host physical address if -cpu max option is applied
Date: Wed, 13 Jan 2021 23:04:29 +0800	[thread overview]
Message-ID: <20210113150429.GA29878@local-michael-cet-test.sh.intel.com> (raw)
In-Reply-To: <5dd8016f-dc18-ee4d-c150-5deabe60e559@redhat.com>

On Wed, Jan 13, 2021 at 11:06:09AM +0100, Paolo Bonzini wrote:
> On 13/01/21 10:04, Yang Weijiang wrote:
> > QEMU option -cpu max(max_features) means "Enables all features supported by
> > the accelerator in the current host", this looks true for all the features
> > except guest max physical address width, so add this patch to enable it.
> > 
> > Signed-off-by: Yang Weijiang <weijiang.yang@intel.com>
> > ---
> >   target/i386/cpu.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > index 35459a38bb..b5943406f7 100644
> > --- a/target/i386/cpu.c
> > +++ b/target/i386/cpu.c
> > @@ -6673,7 +6673,7 @@ static void x86_cpu_realizefn(DeviceState *dev, Error **errp)
> >                   warned = true;
> >               }
> > -            if (cpu->host_phys_bits) {
> > +            if (cpu->host_phys_bits || cpu->max_features) {
> >                   /* The user asked for us to use the host physical bits */
> >                   cpu->phys_bits = host_phys_bits;
> >                   if (cpu->host_phys_bits_limit &&
> > 
> 
> Can you check if this works?
> 
Hi, Paolo,
Yes, below change works for kvm-unit-test/access. Would you add the
patch? 

Thanks!

> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index 35459a38bb..72a79e6019 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -4319,6 +4319,7 @@ static void max_x86_cpu_initfn(Object *obj)
>          if (lmce_supported()) {
>              object_property_set_bool(OBJECT(cpu), "lmce", true,
> &error_abort);
>          }
> +        object_property_set_bool(OBJECT(cpu), "host-phys-bits", true,
> &error_abort);
>      } else {
>          object_property_set_str(OBJECT(cpu), "vendor", CPUID_VENDOR_AMD,
>                                  &error_abort);
> 
> 
> It should allow people to use -cpu max,host-phys-bits=false.
> 
> Thanks,
> 
> Paolo


  reply	other threads:[~2021-01-13 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13  9:04 [Qemu-devel][PATCH] x86/cpu: Use max host physical address if -cpu max option is applied Yang Weijiang
2021-01-13 10:06 ` Paolo Bonzini
2021-01-13 15:04   ` Yang Weijiang [this message]
2021-01-13 15:41     ` Paolo Bonzini
2021-01-24 21:08 ` Nathan Chancellor
2021-01-25  5:41   ` Yang Weijiang
2021-01-25  7:10     ` Nathan Chancellor
2021-01-25 10:42       ` Paolo Bonzini
2021-01-25 18:19         ` Nathan Chancellor

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=20210113150429.GA29878@local-michael-cet-test.sh.intel.com \
    --to=weijiang.yang@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seanjc@google.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).