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 v4 5/5] x86: Set physical address bits based on host
Date: Mon, 11 Jul 2016 19:47:47 +0100	[thread overview]
Message-ID: <20160711184746.GH2078@work-vm> (raw)
In-Reply-To: <20160711184249.GW4131@thinpad.lan.raisama.net>

* Eduardo Habkost (ehabkost@redhat.com) wrote:
> On Mon, Jul 11, 2016 at 04:39:22PM +0100, Dr. David Alan Gilbert wrote:
> > * Eduardo Habkost (ehabkost@redhat.com) wrote:
> [...]
> > > > +            cpu->phys_bits = TCG_PHYS_ADDR_BITS;
> > > > +        }
> > > >      } else {
> > > >          /* For 32 bit systems don't use the user set value, but keep
> > > >           * phys_bits consistent with what we tell the guest.
> > > 
> > > Shouldn't we return error if host-phys-bits is set in 32-bit
> > > mode?
> > 
> > I've just realised there's a reason that erroring in this case is a problem.
> > Imagine a future (or downstream) machine type that made host-phys-bits the default;
> > how would it run with a 32bit CPU?
> 
> Oh, that's right. Ignoring it when explicitly set isn't
> intuitive, but we need to be able to ignore it when set by a
> machine compat_props (or if it's enabled by default). And
> creating two separate properties sounds like overkill...
> I'm reluctant, but I think it's OK to ignore it if LM is not set.
> But we need to make sure it's documented somewhere.

OK, I'll add a comment and a note in the commit message.

Dave

> 
> -- 
> Eduardo
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2016-07-11 18:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 15:01 [Qemu-devel] [PATCH v4 0/5] x86: Physical address limit patches Dr. David Alan Gilbert (git)
2016-07-08 15:01 ` [Qemu-devel] [PATCH v4 1/5] x86: Provide TCG_PHYS_ADDR_BITS Dr. David Alan Gilbert (git)
2016-07-08 18:44   ` Eduardo Habkost
2016-07-08 15:01 ` [Qemu-devel] [PATCH v4 2/5] x86: Allow physical address bits to be set Dr. David Alan Gilbert (git)
2016-07-08 18:59   ` Eduardo Habkost
2016-07-08 19:24     ` Paolo Bonzini
2016-07-08 19:25     ` Dr. David Alan Gilbert
2016-07-08 19:50       ` Eduardo Habkost
2016-07-08 23:36   ` Eduardo Habkost
2016-07-09  0:59     ` Richard Henderson
2016-07-09  2:36       ` Eduardo Habkost
2016-07-08 15:01 ` [Qemu-devel] [PATCH v4 3/5] x86: Mask mtrr mask based on CPU physical address limits Dr. David Alan Gilbert (git)
2016-07-08 15:01 ` [Qemu-devel] [PATCH v4 4/5] x86: fill high bits of mtrr mask Dr. David Alan Gilbert (git)
2016-07-08 23:07   ` Eduardo Habkost
2016-07-08 15:01 ` [Qemu-devel] [PATCH v4 5/5] x86: Set physical address bits based on host Dr. David Alan Gilbert (git)
2016-07-08 16:34   ` Paolo Bonzini
2016-07-08 23:16   ` Eduardo Habkost
2016-07-11 12:29     ` Dr. David Alan Gilbert
2016-07-11 13:01       ` Eduardo Habkost
2016-07-11 15:39     ` Dr. David Alan Gilbert
2016-07-11 18:42       ` Eduardo Habkost
2016-07-11 18:47         ` Dr. David Alan Gilbert [this message]
2016-07-09  0:15 ` [Qemu-devel] [PATCH v4 0/5] x86: Physical address limit patches 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=20160711184746.GH2078@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).