public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, c.koehne@beckhoff.com
Cc: p.bruenn@beckhoff.com, Rebecca Cran <rebecca@bsdio.com>,
	Peter Grehan <grehan@freebsd.org>
Subject: Re: [edk2-devel] [PATCH 1/4] OvmfPkg/Bhyve: enable bus enumeration
Date: Wed, 23 Jun 2021 12:59:16 +0200	[thread overview]
Message-ID: <de0442ae-df0b-e9c9-c04d-10aa4550e344@redhat.com> (raw)
In-Reply-To: <20210614090100.7763-2-c.koehne@beckhoff.com>

On 06/14/21 11:00, Corvin Köhne wrote:
> Neccessary for GPU Passthrough of dedicated AMD GPUs. For Linux
> guests, AMD GPUs require that their PCI ROM is processed by UEFI.
> Enable bus enumeration to process the PCI ROM of all devices.
> 
> Signed-off-by: Corvin Köhne <c.koehne@beckhoff.com>
> ---
>  OvmfPkg/Bhyve/BhyveX64.dsc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/OvmfPkg/Bhyve/BhyveX64.dsc b/OvmfPkg/Bhyve/BhyveX64.dsc
> index d8792812ab..ef331d556e 100644
> --- a/OvmfPkg/Bhyve/BhyveX64.dsc
> +++ b/OvmfPkg/Bhyve/BhyveX64.dsc
> @@ -431,7 +431,7 @@
>    gEfiMdeModulePkgTokenSpaceGuid.PcdInstallAcpiSdtProtocol|TRUE
>  
>  [PcdsFixedAtBuild]
> -  gEfiMdeModulePkgTokenSpaceGuid.PcdPciDisableBusEnumeration|TRUE
> +  gEfiMdeModulePkgTokenSpaceGuid.PcdPciDisableBusEnumeration|FALSE
>    gEfiMdeModulePkgTokenSpaceGuid.PcdStatusCodeUseSerial|FALSE
>    gEfiMdeModulePkgTokenSpaceGuid.PcdStatusCodeUseMemory|TRUE
>    gEfiMdeModulePkgTokenSpaceGuid.PcdStatusCodeMemorySize|1
> 

The right approach -- assuming you reach an agreement with Peter -- is
to revert commist c2f24ba3218a and 8c8f886f2755 first (in this order),
then remove the PcdPciDisableBusEnumeration setting from the DSC
altogether (given the DEC default of the PCD being FALSE).

Independently, please use "python3
$EDK_TOOLS_PATH/Scripts/GetMaintainer.py", for determining the propert
set of CC's for every patch in a series.

I have no comments on the other patches (especially the 4th one), as
they are tied to bhyve platform internals, which I'm unfamiliar with.

Thanks
Laszlo


  reply	other threads:[~2021-06-23 10:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14  9:00 [PATCH 0/4] Prepare bhyve's OVMF for GPU-Passthrough c.koehne
2021-06-14  9:00 ` [PATCH 1/4] OvmfPkg/Bhyve: enable bus enumeration Corvin Köhne
2021-06-23 10:59   ` Laszlo Ersek [this message]
2021-06-14  9:00 ` [PATCH 2/4] Revert "OvmfPkg/Bhyve: consume PciHostBridgeLibScan" Corvin Köhne
2021-06-14  9:00 ` [PATCH 3/4] OvmfPkg/Bhyve: add USB support Corvin Köhne
2021-06-14  9:01 ` [PATCH 4/4] OvmfPkg/Bhyve: use static PCI32Base address Corvin Köhne
2021-06-15  6:03 ` [edk2-devel] [PATCH 0/4] Prepare bhyve's OVMF for GPU-Passthrough Peter Grehan

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=de0442ae-df0b-e9c9-c04d-10aa4550e344@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