From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, afish@apple.com
Subject: Re: [edk2-devel] 2nd OVMF question about why InitRootBridge does not set ResourceAssigned?
Date: Tue, 7 Jul 2020 22:21:52 +0200 [thread overview]
Message-ID: <cd048fd3-ac8b-147b-b278-6f04fa25368a@redhat.com> (raw)
In-Reply-To: <dfedc8ac-7099-0689-27ac-a17e5f3f827b@redhat.com>
On 07/07/20 21:59, Laszlo Ersek wrote:
> (Side note: where I say "synthetic", that does not mean "easy to change"
> at all. Coming up with good 32-bit and 64-bit MMIO apertures for the
> PciHostBridgeLib instance was an arduous task. Among other things, this
> originates from the very quirky placement of the 32-bit address ranges
> on i440fx and q35 that are usable for PCI MMIO. QEMU doesn't dictate the
> apertures for the root bridges, but if you allocate an MMIO BAR from an
> inappropriate address range, you're doomed.)
A key commit regarding the above is 49edde15230a ("OvmfPkg/PlatformPei:
set 32-bit UC area at PciBase / PciExBarBase (pc/q35)", 2019-06-03).
It was very difficult to find a 32-bit PCI MMIO aperture, facing any
random guest RAM size, such that we could mark the aperture in
PlatformPei as UC with no more than the 8 variable MTRRs that QEMU provides.
https://bugzilla.tianocore.org/show_bug.cgi?id=1814
https://bugzilla.tianocore.org/show_bug.cgi?id=1859
Thanks
Laszlo
next prev parent reply other threads:[~2020-07-07 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 17:22 2nd OVMF question about why InitRootBridge does not set ResourceAssigned? Andrew Fish
2020-07-07 19:59 ` [edk2-devel] " Laszlo Ersek
2020-07-07 20:21 ` Laszlo Ersek [this message]
2020-07-07 23:08 ` Andrew Fish
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-list 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=cd048fd3-ac8b-147b-b278-6f04fa25368a@redhat.com \
--to=devel@edk2.groups.io \
/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