From: Gerd Hoffmann <kraxel@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, "László Érsek" <lersek@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] q35: split memory at 2G
Date: Wed, 29 May 2019 06:45:14 +0200 [thread overview]
Message-ID: <20190529044514.ycikti2bj2tem2rb@sirius.home.kraxel.org> (raw)
In-Reply-To: <bf45adf2-1594-89b4-6a4d-9af6d9e8ac6e@redhat.com>
On Wed, May 29, 2019 at 03:21:16AM +0200, Paolo Bonzini wrote:
> On 28/05/19 22:48, Gerd Hoffmann wrote:
> > Original q35 behavior was to split memory 2.75 GB, leaving space for the
> > mmconfig bar at 0xb000000 and pci I/O window starting at 0xc0000000.
> >
> > Note: Those machine types have been removed from the qemu codebase
> > meanwhile because they could not be live-migrated so there was little
> > value in keeping them around.
> >
> > With the effort to allow for gigabyte-alignment of guest memory that
> > behavior was changed: The split was moved to 2G, but only in case the
> > memory didn't fit below 2.75 GB.
> >
> > So today the address space between 2G and 2,75G is not used for guest
> > memory in typical use cases, where the guest memory sized at a power of
> > two or a gigabyte number. But if you configure your guest with some odd
> > amout of memory (such as 2.5G) the address space is used.
>
> Wasn't it done to ensure pre-PAE OSes could use as much memory as
> possible? (If you run pre-PAE OSes with more RAM than can fit below 4G,
> you can just reduce the amount of memory and get all the 2.75G).
Well, those guests are better served with 'pc' where we don't need
address space for mmconfig and you can get 3.5G with no trouble and even
a bit more with extra tweaks (see longish comment in hw/i386/pc_piix.c
explaining all the memory handling options).
cheers,
Gerd
prev parent reply other threads:[~2019-05-29 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 20:48 [Qemu-devel] [PATCH] q35: split memory at 2G Gerd Hoffmann
2019-05-28 20:58 ` Eric Blake
2019-05-29 1:21 ` Paolo Bonzini
2019-05-29 2:49 ` Michael S. Tsirkin
2019-05-29 4:47 ` Gerd Hoffmann
2019-06-03 10:25 ` Laszlo Ersek
2019-05-29 4:45 ` Gerd Hoffmann [this message]
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=20190529044514.ycikti2bj2tem2rb@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).