public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: devel@edk2.groups.io, Jordan Justen <jordan.l.justen@intel.com>,
	Pawel Polawski <ppolawsk@redhat.com>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Oliver Steffen <osteffen@redhat.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>
Subject: Re: [PATCH v2 4/4] OvmfPkg/PciHotPlugInitDxe: reserve more mmio space
Date: Thu, 6 Oct 2022 10:50:03 +0200	[thread overview]
Message-ID: <2af33afb-89b9-38e6-8343-7b0981729058@redhat.com> (raw)
In-Reply-To: <20221005050156.y5vcmelhtnbwgcbt@sirius.home.kraxel.org>

On 10/05/22 07:01, Gerd Hoffmann wrote:
> On Tue, Oct 04, 2022 at 05:57:46PM +0200, Laszlo Ersek wrote:
>> On 10/04/22 15:47, Gerd Hoffmann wrote:
>>> In case the 64-bit pci mmio window is larger than the default size
>>> of 32G be generous and hand out larger chunks of address space for
>>> prefetchable mmio bridge windows.
> 
>>> +      SetMmioPadding (
>>> +        --FirstResource,
>>> +        TRUE,
>>> +        FALSE,
>>> +        (UINTN)HighBitSetRoundUp64 (RShiftU64 (Pci64Size, 8))
>>> +        );
> 
>> Looks good to me, thanks; I'm just missing the rationale on the
>> RShiftU64() call. Please elaborate.
> 
> Cover letter explains this a bit.  The idea is to scale things up with
> the available address space.  Patch #3 does that for the 64-bit pci mmio
> window.  This patch does the same for the bridge windows, leveraging the
> patch #3 calculations by looking at PcdPciMmio64Size.  The shift by 8
> assigns 1/256 of the total mmio window size to each bridge.
> 
> The '8' is just pulled out of thin air.  Looks reasonable to me, in case
> it turns out it is not we can adjust that in the future.

OK, starting with a 64GB aperture size, 256MB will be reserved per port
/ bridge.

For this patch:

Reviewed-by: Laszlo Ersek <lersek@redhat.com>

Laszlo


  reply	other threads:[~2022-10-06  8:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 13:47 [PATCH v2 0/4] OvmfPkg: make better use of physical address space Gerd Hoffmann
2022-10-04 13:47 ` [PATCH v2 1/4] OvmfPkg/PlatformInitLib: qemu cpuid physbits detection Gerd Hoffmann
2022-10-04 13:47 ` [PATCH v2 2/4] OvmfPkg/PlatformInitLib: detect physical address space Gerd Hoffmann
2023-03-16 13:58   ` f.ebner
2023-03-16 14:37     ` Gerd Hoffmann
2023-03-17 11:34       ` [edk2-devel] " Fiona Ebner
2023-03-17 14:01     ` Gerd Hoffmann
2023-03-20 14:20       ` Fiona Ebner
2023-03-20 15:58         ` Gerd Hoffmann
2022-10-04 13:47 ` [PATCH v2 3/4] OvmfPkg/PlatformInitLib: dynamic mmio window size Gerd Hoffmann
2023-03-15  8:54   ` [edk2-devel] " joeyli
2023-03-15  9:28     ` Gerd Hoffmann
2023-05-16 14:00   ` Fiona Ebner
2023-05-17  5:59     ` [edk2-devel] " Gerd Hoffmann
2023-05-17 13:38       ` Fiona Ebner
2023-05-22 11:12         ` Gerd Hoffmann
2023-05-22 13:36           ` Fiona Ebner
2022-10-04 13:47 ` [PATCH v2 4/4] OvmfPkg/PciHotPlugInitDxe: reserve more mmio space Gerd Hoffmann
2022-10-04 15:57   ` Laszlo Ersek
2022-10-05  5:01     ` Gerd Hoffmann
2022-10-06  8:50       ` Laszlo Ersek [this message]
2022-10-07 21:49 ` [edk2-devel] [PATCH v2 0/4] OvmfPkg: make better use of physical address space Ard Biesheuvel

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=2af33afb-89b9-38e6-8343-7b0981729058@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