From: Laszlo Ersek <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH rebased for-1.8] i386: pc: align gpa<->hpa on 1GB boundary (v6)
Date: Tue, 10 Dec 2013 18:46:12 +0100 [thread overview]
Message-ID: <52A75364.5060505@redhat.com> (raw)
In-Reply-To: <1386690784.15686.30.camel@nilsson.home.kraxel.org>
On 12/10/13 16:53, Gerd Hoffmann wrote:
> On Di, 2013-12-10 at 16:47 +0100, Laszlo Ersek wrote:
>> On 12/10/13 15:53, Gerd Hoffmann wrote:
>>> Hi,
>>>
>>>> If we could make a small guset visible change, it would be simpler to
>>>> always make the PCI hole 1GB in size; it is currently 256MB for i440FX
>>>> and 1.25GB for q35.
>>>
>>> Easy for i440fx.
>>
>> I think it's going to break OVMF again.
>
> Can't see a reason why it should.
PCI enumeration in OVMF assigns resources from a window that starts
exactly above the end of below-4gb-memory. For example, in case of a
2.5GB guest, the frame buffer bar of cirrus can be somewhere just above
2.5GB.
If you change the PCI hole in qemu so that it will start at 3GB, always,
then the ACPI tables exported by qemu will also advertise the big mmio
range starting at 3GB. OVMF will pass those tables through to the OS.
Accordingly, the OS will try to access the framebuffer above 3GB, but
OVMF has configured that bar between 2.5GB and 3GB.
IOW, I think this proposal would undo your [PATCH v2] piix: fix 32bit
pci hole.
I can of course live with whatever PCI hole as long as it is made
available to OVMF through an easy-to-parse fw_cfg file. Then I can sync
the OVMF enumeration to qemu's preference.
The fw_cfg file "etc/pci-info" allowed me to do exactly that. But it has
been killed. I'd like it to be resurrected, even if SeaBIOS ignores it.
Thanks,
Laszlo
next prev parent reply other threads:[~2013-12-10 17:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 17:43 [Qemu-devel] [PATCH rebased for-1.8] i386: pc: align gpa<->hpa on 1GB boundary (v6) Paolo Bonzini
2013-11-25 20:58 ` Laszlo Ersek
2013-11-25 21:05 ` Michael S. Tsirkin
2013-11-25 23:09 ` Marcelo Tosatti
2013-11-26 9:04 ` Paolo Bonzini
2013-11-28 10:26 ` Michael S. Tsirkin
2013-12-10 13:18 ` Paolo Bonzini
2013-12-10 14:53 ` Gerd Hoffmann
2013-12-10 14:58 ` Paolo Bonzini
2013-12-10 15:36 ` Gerd Hoffmann
2013-12-10 15:47 ` Laszlo Ersek
2013-12-10 15:53 ` Gerd Hoffmann
2013-12-10 17:46 ` Laszlo Ersek [this message]
2013-12-10 17:48 ` Paolo Bonzini
2013-12-10 21:00 ` Michael S. Tsirkin
2013-12-10 22:13 ` Laszlo Ersek
2013-12-10 22:15 ` Laszlo Ersek
2013-12-10 23:17 ` Michael S. Tsirkin
2013-12-11 8:00 ` Gerd Hoffmann
2013-12-10 15:05 ` Marcelo Tosatti
2013-12-10 17:21 ` Marcelo Tosatti
2013-12-10 21:02 ` Michael S. Tsirkin
2013-12-11 13:41 ` Marcelo Tosatti
2013-12-11 14:20 ` Michael S. Tsirkin
2013-12-11 14:45 ` Paolo Bonzini
2013-12-11 15:39 ` Michael S. Tsirkin
2013-12-11 15:41 ` Paolo Bonzini
2013-12-11 15:51 ` Michael S. Tsirkin
2013-12-11 15:45 ` Igor Mammedov
2013-12-11 15:56 ` Paolo Bonzini
2013-12-11 17:26 ` Marcelo Tosatti
2013-12-10 16:52 ` Michael S. Tsirkin
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=52A75364.5060505@redhat.com \
--to=lersek@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@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).