From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH v2] x86: gigabyte alignment for ram
Date: Mon, 20 Jan 2014 15:59:07 +0200 [thread overview]
Message-ID: <20140120135907.GB31950@redhat.com> (raw)
In-Reply-To: <1390222725.11527.46.camel@nilsson.home.kraxel.org>
On Mon, Jan 20, 2014 at 01:58:45PM +0100, Gerd Hoffmann wrote:
> On Mo, 2014-01-20 at 13:23 +0200, Michael S. Tsirkin wrote:
> > On Tue, Dec 17, 2013 at 06:56:06PM +0100, Gerd Hoffmann wrote:
> > > > I merged your patch but split it: q35 is separate and piix
> > > > is separate. Would you like me to drop the q35 part then?
> > >
> > > If you are fine with q35 having only 2G lowmem keep it. It's safe.
> > >
> > > We can sort the mmconfig setup afterwards, then check if (and how) we'll
> > > transition to 3G lowmem. Maybe we simply don't after all, with the
> > > world moving to 64bit it doesn't matter that much whenever memory is
> > > mapped above or below 4g. And for old 32bit guests there is always the
> > > option to stick with piix which continues to offers up to 3.5G lowmem.
> > >
> > > cheers,
> > > Gerd
> > >
> >
> > Any update here?
>
> No time to investigate yet, still playing catch-up after xmas holidays &
> being sick.
>
> > I'm worried 2G lowmem is a bit too aggressive, PAE still exists.
>
> piix (with up to 3.5g lowmem) exists too ;)
Yes but I think it's preferable to keep features orthogonal.
> > If we want to support old bios, one way would be to add
> > a new register to enable 3g lowmem.
>
> Do we really want do this (allow guest change RAM mapping)?
>
> I think we should:
> (1) reserve mmconf xbar as motherboard ressource, so it can live within
> PCI0._CRS
I don't think this is possible, PCI FW spec seems to
outlaw this explicitly.
> (2) make PCI0._CRS start at end of lowmem, like it does on piix
This we can do. But we'll have to make a hole for the xbar.
> Then maybe:
> (3) update seabios to place xbar somewhere else
> (4) adjust memory layout.
>
> (1)+(2) are useful anyway. (3)+(4) would allow for 3g lowmem, and
> obviously have some compatibility issues: doing (4) requires a seabios
> update.
>
> cheers,
> Gerd
Right. So you'll look into 4 then? I'm keeping these
patches out of tree for now ...
next prev parent reply other threads:[~2014-01-20 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 9:11 [Qemu-devel] [PATCH v2] x86: gigabyte alignment for ram Gerd Hoffmann
2013-12-16 11:54 ` Michael S. Tsirkin
2013-12-16 13:46 ` Gerd Hoffmann
2013-12-16 19:28 ` Michael S. Tsirkin
2013-12-17 10:54 ` Gerd Hoffmann
2013-12-17 11:59 ` Michael S. Tsirkin
2013-12-17 17:56 ` Gerd Hoffmann
2013-12-18 10:05 ` Michael S. Tsirkin
2014-01-20 11:23 ` Michael S. Tsirkin
2014-01-20 12:58 ` Gerd Hoffmann
2014-01-20 13:59 ` Michael S. Tsirkin [this message]
2014-01-20 14:01 ` Gerd Hoffmann
2014-01-20 14:22 ` Michael S. Tsirkin
2014-01-20 15:36 ` Gerd Hoffmann
2014-01-20 15:51 ` Michael S. Tsirkin
2014-01-20 17:15 ` Igor Mammedov
2014-01-21 7:27 ` 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=20140120135907.GB31950@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@amazon.com \
--cc=kraxel@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).