public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: [PATCH 1/5] ArmVirtPkg/PciHostBridgeDxe: don't set linux, pci-probe-only DT property
Date: Wed, 24 Aug 2016 07:30:21 +0200	[thread overview]
Message-ID: <CAKv+Gu_bZfYJ8F2VxYAkufNddeXLx7JhDCi=KWZ6p-C=ZzgAhw@mail.gmail.com> (raw)
In-Reply-To: <679bfdec-9bec-18b9-ba2c-d27669f93fef@redhat.com>

On 23 August 2016 at 23:23, Laszlo Ersek <lersek@redhat.com> wrote:
> On 08/22/16 02:35, Ard Biesheuvel wrote:
>> Setting the linux,pci-probe-only was intended to align OSes booting via
>> DT with OSes booting via ACPI in the way they honor the PCI configuration
>> performed by the firmware. However, ACPI on arm64 does not currently honor
>> the firmware's PCI configuration, and the linux,pci-probe-only completely
>> prevents any PCI reconfiguration from occurring under the OS, including
>> what is needed to support PCI hotplug.
>>
>> Since the primary use case was OS access to the GOP framebuffer (which
>> breaks when the framebuffer BAR is moved when the OS reconfigures the
>> PCI), we can undo this change now that ArmVirtQemu has moved to a GOP
>> implementation that does not expose a raw framebuffer in the first place.
>>
>> Contributed-under: TianoCore Contribution Agreement 1.0
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> ---
>>  ArmVirtPkg/PciHostBridgeDxe/PciHostBridge.c | 38 --------------------
>>  1 file changed, 38 deletions(-)
>>
>> diff --git a/ArmVirtPkg/PciHostBridgeDxe/PciHostBridge.c b/ArmVirtPkg/PciHostBridgeDxe/PciHostBridge.c
>> index 5063782bb392..669c90355889 100644
>> --- a/ArmVirtPkg/PciHostBridgeDxe/PciHostBridge.c
>> +++ b/ArmVirtPkg/PciHostBridgeDxe/PciHostBridge.c
>> @@ -79,42 +79,6 @@ PCI_HOST_BRIDGE_INSTANCE mPciHostBridgeInstanceTemplate = {
>>  // Implementation
>>  //
>>
>> -STATIC
>> -VOID
>> -SetLinuxPciProbeOnlyProperty (
>> -  IN FDT_CLIENT_PROTOCOL         *FdtClient
>> -  )
>> -{
>> -  INT32         Node;
>> -  UINT32        Tmp;
>> -  EFI_STATUS    Status;
>> -
>> -  if (!FeaturePcdGet (PcdPureAcpiBoot)) {
>> -    //
>> -    // Set the /chosen/linux,pci-probe-only property to 1, so that the PCI
>> -    // setup we will perform in the firmware is honored by the Linux OS,
>> -    // rather than torn down and done from scratch. This is generally a more
>> -    // sensible approach, and aligns with what ACPI based OSes do typically.
>> -    //
>> -    // In case we are exposing an emulated VGA PCI device to the guest, which
>> -    // may subsequently get exposed via the Graphics Output protocol and
>> -    // driven as an efifb by Linux, we need this setting to prevent the
>> -    // framebuffer from becoming unresponsive.
>> -    //
>> -    Status = FdtClient->GetOrInsertChosenNode (FdtClient, &Node);
>> -
>> -    if (!EFI_ERROR (Status)) {
>> -      Tmp = SwapBytes32 (1);
>> -      Status = FdtClient->SetNodeProperty (FdtClient, Node,
>> -                            "linux,pci-probe-only", &Tmp, sizeof (Tmp));
>> -    }
>> -    if (EFI_ERROR (Status)) {
>> -      DEBUG ((EFI_D_WARN,
>> -        "Failed to set /chosen/linux,pci-probe-only property\n"));
>> -    }
>> -  }
>> -}
>> -
>>  //
>>  // We expect the "ranges" property of "pci-host-ecam-generic" to consist of
>>  // records like this.
>> @@ -293,8 +257,6 @@ ProcessPciHost (
>>    //
>>    ASSERT (PcdGet64 (PcdPciExpressBaseAddress) == ConfigBase);
>>
>> -  SetLinuxPciProbeOnlyProperty (FdtClient);
>> -
>>    DEBUG ((EFI_D_INFO, "%a: Config[0x%Lx+0x%Lx) Bus[0x%x..0x%x] "
>>      "Io[0x%Lx+0x%Lx)@0x%Lx Mem[0x%Lx+0x%Lx)@0x%Lx\n", __FUNCTION__, ConfigBase,
>>      ConfigSize, *BusMin, *BusMax, *IoBase, *IoSize, *IoTranslation, *MmioBase,
>>
>
> I suggest to note in the commit message that this patch effectively
> undoes commit 8b816c624dd407e1590d7c399c69ab307af3ef33. Can be done
> without a resend, if you agree.
>

Yes, that makes sense.

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

Thanks


  reply	other threads:[~2016-08-24  5:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22  6:35 [PATCH 0/5] ArmVirtQemu: move to generic PciHostBridgeDxe Ard Biesheuvel
2016-08-22  6:35 ` [PATCH 1/5] ArmVirtPkg/PciHostBridgeDxe: don't set linux, pci-probe-only DT property Ard Biesheuvel
2016-08-23 21:23   ` Laszlo Ersek
2016-08-24  5:30     ` Ard Biesheuvel [this message]
2016-08-22  6:35 ` [PATCH 2/5] ArmVirtPkg: implement FdtPciHostBridgeLib Ard Biesheuvel
2016-08-24 15:01   ` Laszlo Ersek
2016-08-24 15:19     ` Ard Biesheuvel
2016-08-31 13:51       ` Laszlo Ersek
2016-08-31 13:54         ` Ard Biesheuvel
2016-08-22  6:35 ` [PATCH 3/5] ArmVirtPkg/ArmVirtQemu: switch to generic PciHostBridgeDxe Ard Biesheuvel
2016-08-23 18:04   ` Ard Biesheuvel
2016-08-31 12:24     ` Laszlo Ersek
2016-08-22  6:35 ` [PATCH 4/5] ArmVirtPkg/FdtPciHostBridgeLib: add MMIO64 support Ard Biesheuvel
2016-08-31 14:06   ` Laszlo Ersek
2016-08-22  6:35 ` [PATCH 5/5] ArmVirtPkg: remove now unused PciHostBridgeDxe Ard Biesheuvel
2016-08-31 14:11   ` Laszlo Ersek
2016-08-22 11:58 ` [PATCH 0/5] ArmVirtQemu: move to generic PciHostBridgeDxe Laszlo Ersek

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='CAKv+Gu_bZfYJ8F2VxYAkufNddeXLx7JhDCi=KWZ6p-C=ZzgAhw@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