qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, marcel@redhat.com,
	mst@redhat.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 4/6] x86: Set physical address bits based on host
Date: Tue, 5 Jul 2016 09:44:45 +0100	[thread overview]
Message-ID: <20160705084445.GB2118@work-vm> (raw)
In-Reply-To: <20160704202717.GJ4131@thinpad.lan.raisama.net>

* Eduardo Habkost (ehabkost@redhat.com) wrote:
> On Mon, Jul 04, 2016 at 08:16:07PM +0100, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> > 
> > A special case based on the previous phys-bits property; if it's
> > the magic value 0 then use the hosts capabilities.
> > 
> > This becomes the default on new machine types.
> > 
> > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > ---
> >  include/hw/i386/pc.h |  5 +++++
> >  target-i386/cpu.c    | 36 +++++++++++++++++++++++++++++++++++-
> >  2 files changed, 40 insertions(+), 1 deletion(-)
> > 
> > diff --git a/include/hw/i386/pc.h b/include/hw/i386/pc.h
> > index d85e924..bf31609 100644
> > --- a/include/hw/i386/pc.h
> > +++ b/include/hw/i386/pc.h
> > @@ -379,6 +379,11 @@ bool e820_get_entry(int, uint32_t, uint64_t *, uint64_t *);
> >          .driver = TYPE_X86_CPU,\
> >          .property = "fill-mtrr-mask",\
> >          .value = "off",\
> > +    },\
> > +    {\
> > +        .driver = TYPE_X86_CPU,\
> > +        .property = "phys-bits",\
> > +        .value = "40",\
> >      },
> >  
> >  #define PC_COMPAT_2_5 \
> > diff --git a/target-i386/cpu.c b/target-i386/cpu.c
> > index 5737aba..d45d2a6 100644
> > --- a/target-i386/cpu.c
> > +++ b/target-i386/cpu.c
> > @@ -2957,6 +2957,40 @@ static void x86_cpu_realizefn(DeviceState *dev, Error **errp)
> >             & CPUID_EXT2_AMD_ALIASES);
> >      }
> >  
> > +    /* For 64bit systems think about the number of physical bits to present.
> > +     * ideally this should be the same as the host; anything other than matching
> > +     * the host can cause incorrect guest behaviour.
> > +     * QEMU used to pick the magic value of 40 bits that corresponds to
> > +     * consumer AMD devices but nothing esle.
> > +     */
> > +    if (env->features[FEAT_8000_0001_EDX] & CPUID_EXT2_LM) {
> > +        uint32_t eax;
> > +        /* Read the hosts physical address size, and compare it to what we
> > +         * were asked for; note old machine types default to 40 bits
> > +         */
> > +        uint32_t host_phys_bits = 0;
> > +        host_cpuid(0x80000000, 0, &eax, NULL, NULL, NULL);
> > +        if (eax >= 0x80000008) {
> > +            host_cpuid(0x80000008, 0, &eax, NULL, NULL, NULL);
> > +            /* Note: According to AMD doc 25481 rev 2.34 they have a field
> > +             * at 23:16 that can specify a maximum physical address bits for
> > +             * the guest that can override this value; but I've not seen
> > +             * anything with that set.
> > +             */
> > +            host_phys_bits = eax & 0xff;
> > +        } else {
> > +            /* It's an odd 64 bit machine that doesn't have the leaf for
> > +             * physical address bits; fall back to 36 that's most older Intel.
> > +             */
> > +            host_phys_bits = 36;
> > +        }
> 
> Why do we need to calculate host_phys_bits when phys_bits is
> already set? Shouldn't we put all the code above after the "if
> (cpu->phys_bits)" check?

Because I reuse host_phys_bits to generate the warning if you've
explicitly set phys-bits and it doesn't match the host.

> > +
> > +        if (cpu->phys_bits == 0) {
> > +            /* The user asked for us to use the host physical bits */
> > +            cpu->phys_bits = host_phys_bits;
> > +
> > +        }
> > +    }
> >  
> >      cpu_exec_init(cs, &error_abort);
> >  
> > @@ -3259,7 +3293,7 @@ static Property x86_cpu_properties[] = {
> >      DEFINE_PROP_BOOL("enforce", X86CPU, enforce_cpuid, false),
> >      DEFINE_PROP_BOOL("kvm", X86CPU, expose_kvm, true),
> >      DEFINE_PROP_BOOL("fill-mtrr-mask", X86CPU, fill_mtrr_mask, true),
> > -    DEFINE_PROP_UINT32("phys-bits", X86CPU, phys_bits, 40),
> > +    DEFINE_PROP_UINT32("phys-bits", X86CPU, phys_bits, 0),
> 
> I would put this part (that sets the default to 0) and the
> PC_COMPAT_2_6 part in a separate patch. This way we can include
> the mechanism for setting phys-bits=0 even if we didn't reach a
> conclusion about the proper pc-2.7 default yet.

Will do.

Dave

> 
> >      DEFINE_PROP_UINT32("level", X86CPU, env.cpuid_level, 0),
> >      DEFINE_PROP_UINT32("xlevel", X86CPU, env.cpuid_xlevel, 0),
> >      DEFINE_PROP_UINT32("xlevel2", X86CPU, env.cpuid_xlevel2, 0),
> > -- 
> > 2.7.4
> > 
> 
> -- 
> Eduardo
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2016-07-05  8:44 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 19:16 [Qemu-devel] [PATCH v2 0/6] x86: Physical address limit patches Dr. David Alan Gilbert (git)
2016-07-04 19:16 ` [Qemu-devel] [PATCH v2 1/6] x86: Allow physical address bits to be set Dr. David Alan Gilbert (git)
2016-07-04 19:33   ` Eduardo Habkost
2016-07-05 13:43     ` Dr. David Alan Gilbert
2016-07-04 19:16 ` [Qemu-devel] [PATCH v2 2/6] x86: Mask mtrr mask based on CPU physical address limits Dr. David Alan Gilbert (git)
2016-07-04 20:02   ` Michael S. Tsirkin
2016-07-04 20:05     ` Eduardo Habkost
2016-07-04 22:37       ` Michael S. Tsirkin
2016-07-04 20:03   ` Eduardo Habkost
2016-07-04 19:16 ` [Qemu-devel] [PATCH v2 3/6] x86: fill high bits of mtrr mask Dr. David Alan Gilbert (git)
2016-07-04 20:03   ` Michael S. Tsirkin
2016-07-04 20:14     ` Eduardo Habkost
2016-07-04 20:21   ` Eduardo Habkost
2016-07-05  8:39     ` Dr. David Alan Gilbert
2016-07-04 19:16 ` [Qemu-devel] [PATCH v2 4/6] x86: Set physical address bits based on host Dr. David Alan Gilbert (git)
2016-07-04 20:27   ` Eduardo Habkost
2016-07-05  8:44     ` Dr. David Alan Gilbert [this message]
2016-07-04 19:16 ` [Qemu-devel] [PATCH v2 5/6] x86: fix up 32 bit phys_bits case Dr. David Alan Gilbert (git)
2016-07-05  9:42   ` Daniel P. Berrange
2016-07-05 11:29     ` Dr. David Alan Gilbert
2016-07-05 11:55       ` Daniel P. Berrange
2016-07-05 19:05         ` Dr. David Alan Gilbert
2016-07-04 19:16 ` [Qemu-devel] [PATCH v2 6/6] x86: Add sanity checks on phys_bits Dr. David Alan Gilbert (git)
2016-07-04 20:46   ` Eduardo Habkost
2016-07-05 10:40     ` Dr. David Alan Gilbert
2016-07-04 20:23 ` [Qemu-devel] [PATCH v2 0/6] x86: Physical address limit patches Michael S. Tsirkin
2016-07-05  9:33   ` Dr. David Alan Gilbert
2016-07-05 10:06     ` Michael S. Tsirkin
2016-07-05 10:13       ` Dr. David Alan Gilbert
2016-07-05 10:41         ` Michael S. Tsirkin
2016-07-05 10:59       ` Paolo Bonzini
2016-07-05 11:09         ` Michael S. Tsirkin
2016-07-05 11:46           ` Paolo Bonzini
2016-07-05 12:39             ` Michael S. Tsirkin
2016-07-05 12:41           ` Dr. David Alan Gilbert
2016-07-05 13:38             ` Michael S. Tsirkin
2016-07-05  9:46 ` Daniel P. Berrange
2016-07-05  9:49   ` Dr. David Alan Gilbert
2016-07-05 12:38     ` Eduardo Habkost

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=20160705084445.GB2118@work-vm \
    --to=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 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).