From: Don Slutz <dslutz@verizon.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Don Slutz <dslutz@verizon.com>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] pc & q35: fix handling of lowmem
Date: Fri, 28 Feb 2014 10:14:37 -0500 [thread overview]
Message-ID: <5310A7DD.4060003@terremark.com> (raw)
In-Reply-To: <1393594506.3364.65.camel@nilsson.home.kraxel.org>
On 02/28/14 08:35, Gerd Hoffmann wrote:
> On Do, 2014-02-27 at 15:01 -0500, Don Slutz wrote:
>> Without this, asking for 3.25G on memory for pc-i440fx-2.0 does not
>> adjust the pci hole to start at 3G. Asking for 3.75G does do this
>> adjustment.
> This is intentional.
>
> If we can fit all ram into low memory, because it is less than 3.5G,
> we'll do that (pc machine type, q35 numbers are different but logic is
> the same). This way 32bit (+non-PAE) guests can continue to have up to
> 3.5G memory.
>
> If we can't fit all ram into low memory (thus the guest should be able
> to access ram above 4G anyway), then we'll cut off at a gigabyte
> boundary (3G for pc machine type). This way our ram is nicely
> gigabyte-aligned and we can get best performance benefits from huge
> pages.
>
> The size of the pci hole changing in the second case is only a side
> effect, it's not the main reason for the change.
>
> cheers,
> Gerd
>
>
Ok, I will drop this patch.
-Don Slutz
prev parent reply other threads:[~2014-02-28 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 20:01 [Qemu-devel] [PATCH 1/1] pc & q35: fix handling of lowmem Don Slutz
2014-02-28 13:35 ` Gerd Hoffmann
2014-02-28 15:14 ` Don Slutz [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=5310A7DD.4060003@terremark.com \
--to=dslutz@verizon.com \
--cc=aliguori@amazon.com \
--cc=kraxel@redhat.com \
--cc=mst@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).