public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, kraxel@redhat.com
Cc: 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: [edk2-devel] [PATCH v2 0/4] OvmfPkg: make better use of physical address space.
Date: Fri, 7 Oct 2022 23:49:40 +0200	[thread overview]
Message-ID: <CAMj1kXF7QDDHC19FGVxKM_s-pYsNRtsvkHFOMsYMztd1Kd5K_A@mail.gmail.com> (raw)
In-Reply-To: <20221004134728.55499-1-kraxel@redhat.com>

Merged #3449 into master.

On Tue, 4 Oct 2022 at 15:47, Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> For historical reasons ovmf is quite conservative on address space
> usage, to play safe and avoid using more than 36 physical address bits
> (the guaranteed minimum) if possible.  With devices (specifically GPUs)
> becoming larger and larger pci memory bars this becomes increasingly
> problematic.
>
> This patch series address that by trying to figure what the physical
> address space size is (which is a bit tricky, see patch #1 for details).
> If that worked scale up the 64-bit mmio window and also pcie bridge
> windows dynamically with the available address space.
>
> v2:
>  - fix pcie bridge window logic, track prefetchable and non-prefetchable
>    default state separately (Laszlo).
>
> Gerd Hoffmann (4):
>   OvmfPkg/PlatformInitLib: qemu cpuid physbits detection
>   OvmfPkg/PlatformInitLib: detect physical address space
>   OvmfPkg/PlatformInitLib: dynamic mmio window size
>   OvmfPkg/PciHotPlugInitDxe: reserve more mmio space
>
>  OvmfPkg/PciHotPlugInitDxe/PciHotPlugInit.inf |   1 +
>  OvmfPkg/Library/PlatformInitLib/MemDetect.c  | 143 ++++++++++++++++---
>  OvmfPkg/PciHotPlugInitDxe/PciHotPlugInit.c   |  21 ++-
>  3 files changed, 145 insertions(+), 20 deletions(-)
>
> --
> 2.37.3
>
>
>
> 
>
>

      parent reply	other threads:[~2022-10-07 21:49 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
2022-10-07 21:49 ` Ard Biesheuvel [this message]

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=CAMj1kXF7QDDHC19FGVxKM_s-pYsNRtsvkHFOMsYMztd1Kd5K_A@mail.gmail.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