From: Gleb Natapov <gleb@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix guest physical bits to match host, to go beyond 1TB guests
Date: Wed, 17 Jul 2013 18:19:28 +0300 [thread overview]
Message-ID: <20130717151928.GF13732@redhat.com> (raw)
In-Reply-To: <20130716194238.GG11420@otherpad.lan.raisama.net>
On Tue, Jul 16, 2013 at 04:42:38PM -0300, Eduardo Habkost wrote:
> On Tue, Jul 16, 2013 at 09:24:30PM +0200, Paolo Bonzini wrote:
> > Il 16/07/2013 20:11, Eduardo Habkost ha scritto:
> > > For physical bit size, what about extending it in a backwards-compatible
> > > way? Something like this:
> > >
> > > *eax = 0x0003000; /* 48 bits virtual */
> > > if (ram_size < 1TB) {
> > > physical_size = 40; /* Keeping backwards compatibility */
> > > } else if (ram_size < 4TB) {
> > > physical_size = 42;
> >
> > Why not go straight up to 44?
>
> I simply trusted the comment saying: "The physical address space is
> limited to 42 bits in exec.c", and assumed we had a 42-bit limit
> somewhere else.
>
> We could also try something like this:
>
> if (ram_size < 1TB) {
> physical_size = 40; /* Keeping backwards compatibility */
> } else {
> physical_size = msb(ram_size);
> }
> if (supported_host_physical_size() < physical_size) {
> abort();
> }
>
>
ram_size is the things we set with -m, right? Because if it is then
using it here is incorrect since, due to PCI hole, max phys address is
higher than ram_size.
--
Gleb.
next prev parent reply other threads:[~2013-07-17 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 17:22 [Qemu-devel] [PATCH] fix guest physical bits to match host, to go beyond 1TB guests Andrea Arcangeli
2013-07-16 17:26 ` Paolo Bonzini
2013-07-16 17:38 ` Eduardo Habkost
2013-07-16 17:46 ` Paolo Bonzini
2013-07-16 17:48 ` Paolo Bonzini
2013-07-16 18:06 ` Andrea Arcangeli
2013-07-16 18:11 ` Eduardo Habkost
2013-07-16 19:24 ` Paolo Bonzini
2013-07-16 19:42 ` Eduardo Habkost
2013-07-17 8:09 ` Paolo Bonzini
2013-07-17 13:39 ` Eduardo Habkost
2013-07-17 14:01 ` Paolo Bonzini
2013-07-17 15:19 ` Gleb Natapov [this message]
2013-07-17 21:20 ` 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=20130717151928.GF13732@redhat.com \
--to=gleb@redhat.com \
--cc=aarcange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).