From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2] pc: allow raising low memory via max-ram-below-4g option
Date: Mon, 11 Jan 2016 09:26:20 +0100 [thread overview]
Message-ID: <1452500780.8098.27.camel@redhat.com> (raw)
In-Reply-To: <569000C2.7050809@redhat.com>
On Fr, 2016-01-08 at 19:32 +0100, Laszlo Ersek wrote:
> On 01/08/16 18:45, Igor Mammedov wrote:
> > On Fri, 8 Jan 2016 13:58:03 +0100
> > Gerd Hoffmann <kraxel@redhat.com> wrote:
> >
> >> This patch extends the functionality of the max-ram-below-4g option
> >> to also allow increasing lowmem. Use case: Give as much memory as
> >> possible to legacy non-PAE guests.
> >>
> >> While being at it also rework the lowmem calculation logic and add a
> >> longish comment describing how it works and what the compatibility
> >> constrains are.
> > CCing Laszlo as it might affect OVMF
>
> Thanks a lot for the CC, Igor!
>
> So I have to investigate this separately for i440fx and Q35.
>
> (1) For i440fx, OVMF determines the base of the 32-bit PCI hole like this:
>
> PciBase = (TopOfLowRam < BASE_2GB) ? BASE_2GB : TopOfLowRam;
>
> where TopOfLowRam is calculated from the CMOS registers 0x34 and 0x35.
>
> *If* QEMU is still sticking with the idea of git commit ddaaefb4dd, that
> is, the 32-bit PCI hole still starts immediately after the end of low
> RAM, then this change should be fine for i440fx.
Good.
> Gerd, can you confirm that this new logic for the lowmem/highmem split
> doesn't affect the above?
>
> In other words, as long as there is no "void" left between the top of
> low RAM and the base of the PCI hole, it doesn't matter where exactly
> the split is.
Yes, the logic is the same as before. Anything above ram is pci i/o.
> (2) For Q35, the OVMF code is different:
The patch doesn't change q35 behavior.
cheers,
Gerd
next prev parent reply other threads:[~2016-01-11 8:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 12:58 [Qemu-devel] [PATCH v2] pc: allow raising low memory via max-ram-below-4g option Gerd Hoffmann
2016-01-08 17:45 ` Igor Mammedov
2016-01-08 18:32 ` Laszlo Ersek
2016-01-11 8:26 ` Gerd Hoffmann [this message]
2016-01-11 12:16 ` Laszlo Ersek
2016-01-11 12:26 ` Marcel Apfelbaum
2016-01-14 23:45 ` Eric Blake
2016-01-19 12:37 ` Eduardo Habkost
2016-01-20 14:55 ` Gerd Hoffmann
2016-01-20 15:34 ` Eduardo Habkost
2016-01-20 17:15 ` Eduardo Habkost
2016-01-20 17:25 ` Michael S. Tsirkin
2016-01-21 7:48 ` Gerd Hoffmann
2016-01-21 9:37 ` Michael S. Tsirkin
2016-01-22 10:51 ` Gerd Hoffmann
2016-01-24 6:37 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2016-06-02 8:48 Gerd Hoffmann
2015-11-03 10:06 Gerd Hoffmann
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=1452500780.8098.27.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.