From: Liran Alon <liran.alon@oracle.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Nikita Leshenko <nikita.leshchenko@oracle.com>,
edk2-devel@lists.01.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: PciBusDxe: PCI-Express bug with dynamic PcdPciExpressBaseAddress
Date: Fri, 7 Sep 2018 20:01:49 +0300 [thread overview]
Message-ID: <8A63AC46-22FF-480A-A109-9902B7076464@oracle.com> (raw)
In-Reply-To: <2fdb6059-86a4-a8d5-a46c-286c62e17864@redhat.com>
> On 7 Sep 2018, at 11:44, Laszlo Ersek <lersek@redhat.com> wrote:
>
> (+Ard)
>
> On 09/06/18 21:08, Nikita Leshenko wrote:
>> Hi,
>>
>> We ran into a bug in EDK2 relating to PCI-Express in PciBusDxe. Here's the flow
>> of the bug:
>>
>> 1. PciBusDxe/PciEnumeratorSupport.c: Function BarExisted probes a BAR. It raises
>> TPL to TPL_HIGH_LEVEL to avoid timer interrupts while probing the BAR and
>> calls PciIo->Pci.Write.
>> 2. BasePciExpressLib/PciExpressLib.c: The write reaches PciExpressWrite32, which
>> calls GetPciExpressBaseAddress.
>> 3. GetPciExpressBaseAddress retrieves the address from PcdPciExpressBaseAddress.
>> 4. Reading the PCD calls DxePcdGet64 -> GetWorker ->
>> EfiAcquireLock(&mPcdDatabaseLock), which is at TPL_NOTIFY level. This crashes
>> the firmware because step 1 raised the TPL to TPL_HIGH_LEVEL.
>>
>> This doesn't happen when PcdPciExpressBaseAddress is fixed at build (because
>> then the read is optimized to a static global variable), but when the PCD is
>> dynamic PCI-Express is broken.
>>
>> Does anybody have a suggestion for fixing it?
>>
>> Options we thought about:
>> - Change mPcdDatabaseLock.Tpl to TPL_HIGH_LEVEL
>> - Don't use a PCD for the base address, put it in a static global variable and
>> create functions to set and retrieve it.
>
> In the ArmVirtPkg platforms, we also set "PcdPciExpressBaseAddress"
> dynamically. And, we implemented your second option above; see:
>
> ArmVirtPkg/Library/BaseCachingPciExpressLib/
>
> Relevant commits:
>
> - ad3359eb43a9 ("ArmVirtualizationPkg: clone BasePciExpressLib, cache
> PCIe config base", 2015-02-23)
> - a06d0bb58eb9 ("ArmVirtPkg/BaseCachingPciExpressLib: depend on
> PciPcdProducerLib", 2016-04-12)
>
> (In fact, commit ad3359eb43a9 documents the exact issue you report here.)
>
> Thanks
> Laszlo
Thanks Lazlo. Weren’t aware of this solution in the ArmVirtPkg platforms.
However, I wonder why the solution was to clone the MdePkg/Library/BasePciExpressLib rather than
change the original library itself?
That is, what was the reason for not just adding a library constructor to MdePkg/Library/BasePciExpressLib
to cache PcdPciExpressBaseAddress in a global var? This seem to solve the issues for all platforms.
If PcdPciExpressBaseAddress is fixed and doesn’t change dynamically, then the caching of the value in a global var
should be harmless (besides adding an extra read from global-var). If it does change dynamically,
MdePkg/Library/BasePciExpressLib have the issue discussed in this email thread.
Thanks,
-Liran
next prev parent reply other threads:[~2018-09-07 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 19:08 PciBusDxe: PCI-Express bug with dynamic PcdPciExpressBaseAddress Nikita Leshenko
2018-09-07 0:25 ` Ni, Ruiyu
2018-09-07 8:44 ` Laszlo Ersek
2018-09-07 17:01 ` Liran Alon [this message]
2018-09-11 13:34 ` Laszlo Ersek
2018-09-13 12:27 ` Nikita Leshenko
2018-09-13 13:15 ` Laszlo Ersek
2018-09-16 12:28 ` Nikita Leshenko
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=8A63AC46-22FF-480A-A109-9902B7076464@oracle.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