From: "Joe L" <jlotwo@gmail.com>
To: devel@edk2.groups.io
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Liming Gao <gaoliming@byosoft.com.cn>,
Michael Brown <mcb30@ipxe.org>,
Pedro Falcato <pedro.falcato@gmail.com>,
Ray Ni <ray.ni@intel.com>, Hao A Wu <hao.a.wu@intel.com>,
Jian J Wang <jian.j.wang@intel.com>,
Sami Mujawar <sami.mujawar@arm.com>,
lersek@redhat.com, michael.d.kinney@intel.com
Subject: Re: [edk2-devel] [PATCH v2] MdeModulePkg/PciHostBridgeDxe: Add readback after final Cfg-Write
Date: Tue, 7 Nov 2023 10:58:42 -0800 [thread overview]
Message-ID: <CAMkAJO_p3vYZRm+G9cCASjnA25PJrFmi7jK2bt3XiuAA+BKW_g@mail.gmail.com> (raw)
In-Reply-To: <CAMkAJO8YmSoZi-kDRutZAGpR_qivwTwdMQHSpW92cKAnDTM0=Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3690 bytes --]
++ Laszlo and Michael
On Tue, Nov 7, 2023 at 10:54 AM Jose Lopez <jlotwo@gmail.com> wrote:
> ++ CC'd
>
>
> On Mon, Nov 6, 2023 at 6:02 PM Joe Lopez <jlotwo@gmail.com> wrote:
>
>> From: joelopez333 <jlotwo@gmail.com>
>>
>> REF:https://edk2.groups.io/g/devel/topic/102310377#110456
>>
>> Problem Report:
>>
>> On AARCH64, there is no ordering guarantee between configuration
>> space (ECAM) writes and memory space reads (MMIO). ARM AMBA CHI
>> only guarantees ordering for reads and writes within a single address
>> region,
>> however, on some systems MMIO and ECAM may be split into separate
>> address regions.
>>
>> A problem may arise when an ECAM write is issued a completion before
>> a subsequent
>> MMIO read is issued and receives a completion.
>>
>> For example, a typical PCI software flow is the following:
>>
>> 1. ECAM write to device command register to enable memory space
>> 2. MMIO read from device memory space for which access was enabled
>> in step 1.
>>
>> There is no guarantee that step 2. will not begin before the
>> completion of step 1.
>> on systems where ECAM/MMIO are specified as separate address regions,
>> even
>> if both spaces have the memory attributes device-nGnRnE.
>>
>> Fix:
>>
>> - Add a read after the final PCI Configuration space write
>> in RootBridgeIoPciAccess.
>>
>> - When configuration space is strongly ordered, this ensures
>> that program execution cannot continue until the completion
>> is received for the previous Cfg-Write, which may have side-effects.
>>
>> - Risk of reading a "write-only" register and causing a CA which
>> leaves the device
>> unresponsive. The expectation based on the PCI Base Spec v6.1
>> section 7.4 is that
>> all PCI Spec-defined registers will be readable, however, there may
>> exist
>> design-specific registers that fall into this category.
>>
>> Cc: Leif Lindholm <quic_llindhol@quicinc.com>
>> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
>> Cc: Sami Mujawar <sami.mujawar@arm.com>
>> Cc: Jian J Wang <jian.j.wang@intel.com>
>> Cc: Liming Gao <gaoliming@byosoft.com.cn>
>> Cc: Hao A Wu <hao.a.wu@intel.com>
>> Cc: Ray Ni <ray.ni@intel.com>
>> Cc: Pedro Falcato <pedro.falcato@gmail.com>
>> Cc: Michael Brown <mcb30@ipxe.org>
>> Signed-off-by: Joe Lopez <jlotwo2@gmail.com>
>> ---
>> MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c
>> b/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c
>> index 157a0ada80..c2dc2018d6 100644
>> --- a/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c
>> +++ b/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c
>> @@ -1238,6 +1238,14 @@ RootBridgeIoPciAccess (
>> }
>> }
>>
>> + //
>> + // Perform readback after write to confirm completion was received for
>> the last write
>> + // before subsequent memory operations can be issued.
>> + //
>> + if (!Read) {
>> + PciSegmentRead8 (Address - InStride);
>> + }
>> +
>> return EFI_SUCCESS;
>> }
>>
>> --
>> 2.25.1
>>
>>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#110876): https://edk2.groups.io/g/devel/message/110876
Mute This Topic: https://groups.io/mt/102435564/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 5879 bytes --]
next prev parent reply other threads:[~2023-11-07 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 2:02 [edk2-devel] [PATCH v2] MdeModulePkg/PciHostBridgeDxe: Add readback after final Cfg-Write Joe L
2023-11-07 18:54 ` Joe L
2023-11-07 18:58 ` Joe L [this message]
2023-11-08 1:06 ` Michael D Kinney
2023-11-13 11:37 ` 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=CAMkAJO_p3vYZRm+G9cCASjnA25PJrFmi7jK2bt3XiuAA+BKW_g@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