From: "Gerd Hoffmann via groups.io" <kraxel=redhat.com@groups.io>
To: devel@edk2.groups.io, mitchell.augustin@canonical.com
Subject: Re: [edk2-devel] [BUG] Extremely slow boot times with CPU and GPU passthrough and host phys-bits > 40
Date: Mon, 25 Nov 2024 12:47:16 +0100 [thread overview]
Message-ID: <ikoq6j2yqbskux45nuep45obrkivegremtxvxl6zmq2snxbs3t@mduo6fp4epvf> (raw)
In-Reply-To: <14003.1732413940796322655@groups.io>
On Sat, Nov 23, 2024 at 06:05:40PM -0800, mitchell.augustin via groups.io wrote:
> Hi again,
> I have a more specific version of a prior question: Is there some
> fw_cfg flag that would simply allow me to use the classic MMIO window,
> in effect keeping PlatformInfoHob->PcdPciMmio64Size and
> PlatformInfoHob->PcdPciMmio64Base set to what they would be with the
> PlatformDynamicMmioWindow patch (
> https://github.com/tianocore/edk2/commit/ecb778d0ac62560aa172786ba19521f27bc3f650
> ) disabled?
Not directly. OVMF considers PcdPciMmio64Size being the minimum size.
Rf the dynamic mmio window would be larger it will simply use the
dynamic mmio window, otherwise the PcdPciMmio64Size + PcdPciMmio64Base
values.
The dynamic mmio windos is 1/8 of the address space, i.e. for
phys-bits=42 (4TB address space) the dynamic mmio window size is 512GB.
In that case you can set PcdPciMmio64Size to 1TB and PcdPciMmio64Base to
1 or 2 or 3 TB and OVMF should use these values.
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120831): https://edk2.groups.io/g/devel/message/120831
Mute This Topic: https://groups.io/mt/109651206/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-11-25 11:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 16:46 [edk2-devel] [BUG] Extremely slow boot times with CPU and GPU passthrough and host phys-bits > 40 mitchell.augustin via groups.io
2024-11-18 21:14 ` xpahos via groups.io
2024-11-19 22:25 ` mitchell.augustin via groups.io
2024-11-20 9:35 ` xpahos via groups.io
2024-11-20 11:26 ` Gerd Hoffmann via groups.io
2024-11-20 15:20 ` mitchell.augustin via groups.io
2024-11-20 20:00 ` mitchell.augustin via groups.io
2024-11-21 12:32 ` Gerd Hoffmann via groups.io
2024-11-22 0:23 ` mitchell.augustin via groups.io
2024-11-22 10:35 ` Gerd Hoffmann via groups.io
2024-11-22 17:38 ` Brian J. Johnson via groups.io
2024-11-22 22:32 ` mitchell.augustin via groups.io
2024-11-24 2:05 ` mitchell.augustin via groups.io
2024-11-25 11:47 ` Gerd Hoffmann via groups.io [this message]
2024-11-25 19:58 ` mitchell.augustin via groups.io
2024-11-26 8:09 ` Gerd Hoffmann via groups.io
2024-11-26 22:27 ` mitchell.augustin via groups.io
2024-12-04 14:56 ` mitchell.augustin via groups.io
2024-11-25 11:18 ` Gerd Hoffmann via groups.io
2024-11-18 21:32 ` Ard Biesheuvel via groups.io
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=ikoq6j2yqbskux45nuep45obrkivegremtxvxl6zmq2snxbs3t@mduo6fp4epvf \
--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