From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] piix: fix 32bit pci hole
Date: Wed, 27 Nov 2013 07:46:01 +0100 [thread overview]
Message-ID: <1385534761.13867.9.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <52951398.3010206@redhat.com>
> > + i440fx->pci_info.w32.begin = ram_size;
> But this patch also obliterates the high bound, 0xe0000000, which can
> lead to:
> - w32.end - w32.begin <= 512M, or
> - a special case of the former, w32.end < w32.begin.
ram_size is not the total amount of memory, it is low memory only.
There is another parameter to i440fx_init (above_4g_mem_size) which
holds the amount of memory which is going to be mapped above 4G.
Maximum possible value of ram_size is 0xe0000000.
For completeness: On q35 the maximum amount of low mem is 0xb0000000.
> w32.end is set to IO_APIC_DEFAULT_ADDRESS==0xfec00000. (Which is BTW
> fine for OVMF too.) What will happen in a 6G guest, for example?
ram_size = 0xe0000000
above_4g_mem_size = 0xa0000000
cheers,
Gerd
next prev parent reply other threads:[~2013-11-27 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 16:16 [Qemu-devel] [PATCH] piix: fix 32bit pci hole Gerd Hoffmann
2013-11-26 21:33 ` Laszlo Ersek
2013-11-27 6:46 ` Gerd Hoffmann [this message]
2013-11-27 11:48 ` Laszlo Ersek
2013-11-26 23:36 ` Jordan Justen
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=1385534761.13867.9.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=lersek@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).