From: "Anthony PERARD" <anthony.perard@citrix.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: <devel@edk2.groups.io>, Tom Lendacky <thomas.lendacky@amd.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Erdem Aktas <erdemaktas@google.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Oliver Steffen <osteffen@redhat.com>, Min Xu <min.m.xu@intel.com>,
Michael Roth <michael.roth@amd.com>,
James Bottomley <jejb@linux.ibm.com>,
Pawel Polawski <ppolawsk@redhat.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Julien Grall <julien@xen.org>
Subject: Re: [PATCH v2 2/3] OvmfPkg/PlatformInitLib: move mmconfig to 0xe0000000
Date: Mon, 27 Mar 2023 16:06:03 +0100 [thread overview]
Message-ID: <979ed389-56f4-4fc4-8a2b-7cbfa93143eb@perard> (raw)
In-Reply-To: <20230307065454.1434251-3-kraxel@redhat.com>
On Tue, Mar 07, 2023 at 07:54:53AM +0100, Gerd Hoffmann wrote:
> Also swap the ordering of 32bit PCI MMIO window on q35, i.e. use the
> room between end of low memory and the start of the mmconfig bar.
>
> With a typical configuration on modern qemu with gigabyte-aligned memory
> the MMIO window start at 0x8000000, sized 1532 MB. In case there is
> memory present above 0x80000000 the window will start at 0xc0000000
> instead, with 512 MB size.
>
> This depends on qemu commit 4a4418369d6d ("q35: fix mmconfig and
> PCI0._CRS"), so it raises the bar for the lowest supported version
> to qemu 4.1 (released Aug 2019).
Maybe this new version requirement should be noted in OvmfPkg/README,
but I'm not sure were as it affect only machine started with Q35.
> diff --git a/OvmfPkg/OvmfXen.dsc b/OvmfPkg/OvmfXen.dsc
> index c328987e8432..18144d9a6d94 100644
> --- a/OvmfPkg/OvmfXen.dsc
> +++ b/OvmfPkg/OvmfXen.dsc
> @@ -434,7 +434,7 @@ [PcdsFixedAtBuild]
> #
> # On Q35 machine types that QEMU intends to support in the long term, QEMU
> # never lets the RAM below 4 GB exceed 2816 MB.
> - gEfiMdePkgTokenSpaceGuid.PcdPciExpressBaseAddress|0xB0000000
> + gEfiMdePkgTokenSpaceGuid.PcdPciExpressBaseAddress|0xE0000000
Could you remove this change? OvmfXen doesn't use PlatformInitLib, and
we still have worked to do to be able to use Q35 in Xen guest.
I think the rest looks fine, so:
Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2023-03-27 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 6:54 [PATCH v2 0/3] OvmfPkg/PlatformInitLib: move mmconfig to 0xe0000000 Gerd Hoffmann
2023-03-07 6:54 ` [PATCH v2 1/3] OvmfPkg/PlatformInitLib: update address space layout comment Gerd Hoffmann
2023-03-27 14:59 ` Anthony PERARD
2023-03-07 6:54 ` [PATCH v2 2/3] OvmfPkg/PlatformInitLib: move mmconfig to 0xe0000000 Gerd Hoffmann
2023-03-27 15:06 ` Anthony PERARD [this message]
2023-03-07 6:54 ` [PATCH v2 3/3] OvmfPkg/PlatformInitLib: simplify mtrr setup Gerd Hoffmann
2023-03-27 15:14 ` Anthony PERARD
2023-03-20 9:57 ` [PATCH v2 0/3] OvmfPkg/PlatformInitLib: move mmconfig to 0xe0000000 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-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=979ed389-56f4-4fc4-8a2b-7cbfa93143eb@perard \
--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