From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Ni, Ray" <ray.ni@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"ardb@kernel.org" <ardb@kernel.org>,
Pawel Polawski <ppolawsk@redhat.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
"Gao, Liming" <gaoliming@byosoft.com.cn>,
"Wu, Hao A" <hao.a.wu@intel.com>,
Oliver Steffen <osteffen@redhat.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Chang, Abner" <abner.chang@hpe.com>,
"Wang, Jian J" <jian.j.wang@intel.com>
Subject: Re: [edk2-devel] [PATCH v5 1/6] MdeModulePkg/PciHostBridge: io range is not mandatory
Date: Fri, 29 Apr 2022 08:50:47 +0200 [thread overview]
Message-ID: <20220429065047.7ed7xvawzmfdja2h@sirius.home.kraxel.org> (raw)
In-Reply-To: <MWHPR11MB1631273DF7BA38B555ABF5718CFA9@MWHPR11MB1631.namprd11.prod.outlook.com>
On Wed, Apr 27, 2022 at 03:08:50AM +0000, Ni, Ray wrote:
> Ard,
> can you explain more?
>
> Your code changes the PciHostBridge driver to ignore the failure of IO allocation.
> If IO requirement of certain PCI(E) devices can be ignored, can you change the IncompatiblePciDevice protocol implementation to override the IO request from the devices?
Hmm, it's a problem indeed, device initialization fails in case an
io bar is present even if the bar is not required to drive the device.
Suggestions how to deal with this best? ovmf has it's own
IncompatiblePciDevice Protocol implementation, so I could
handle it there because only OvmfPkg/Microvm needs this.
Or should the MdeModulePkg version be updated too?
thanks,
Gerd
next prev parent reply other threads:[~2022-04-29 6:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 7:37 [PATCH v5 0/6] OvmfPkg/Microvm/pcie: add pcie support Gerd Hoffmann
2022-04-22 7:37 ` [PATCH v5 1/6] MdeModulePkg/PciHostBridge: io range is not mandatory Gerd Hoffmann
2022-04-25 20:49 ` [edk2-devel] " Ard Biesheuvel
2022-04-27 0:32 ` 回复: " gaoliming
2022-04-27 3:08 ` Ni, Ray
2022-04-29 6:50 ` Gerd Hoffmann [this message]
2022-04-29 7:00 ` Ard Biesheuvel
2022-04-29 8:13 ` Ni, Ray
2022-04-29 8:47 ` Gerd Hoffmann
2022-04-29 9:08 ` Ni, Ray
2022-04-29 9:46 ` Gerd Hoffmann
2022-05-02 10:48 ` Gerd Hoffmann
2022-05-23 11:48 ` Albecki, Mateusz
2022-05-24 6:24 ` Gerd Hoffmann
2022-05-25 18:26 ` Albecki, Mateusz
2022-05-31 16:11 ` Gerd Hoffmann
2022-06-02 10:00 ` Ni, Ray
[not found] ` <16E9A2157ED8983D.16936@groups.io>
2022-04-27 3:13 ` Ni, Ray
2022-04-22 7:37 ` [PATCH v5 2/6] OvmfPkg/FdtPciHostBridgeLib: " Gerd Hoffmann
2022-04-22 15:01 ` Abner Chang
2022-04-22 7:37 ` [PATCH v5 3/6] OvmfPkg/Platform: unfix PcdPciExpressBaseAddress Gerd Hoffmann
2022-04-22 7:37 ` [PATCH v5 4/6] OvmfPkg/Microvm/pcie: no vbeshim please Gerd Hoffmann
2022-04-22 7:37 ` [PATCH v5 5/6] OvmfPkg/Microvm/pcie: mPhysMemAddressWidth tweak Gerd Hoffmann
2022-04-22 7:37 ` [PATCH v5 6/6] OvmfPkg/Microvm/pcie: add pcie support 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=20220429065047.7ed7xvawzmfdja2h@sirius.home.kraxel.org \
--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