From: "Laszlo Ersek" <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@arm.com>,
Jiahui Cen <cenjiahui@huawei.com>,
devel@edk2.groups.io
Cc: jordan.l.justen@intel.com, leif@nuviainc.com,
xieyingtai@huawei.com, miaoyubo@huawei.com
Subject: Re: [PATCH v2 0/4] Add extra pci roots support for Arm
Date: Fri, 13 Nov 2020 20:44:16 +0100 [thread overview]
Message-ID: <286c4d14-82f4-6238-2fb1-15e6072fad07@redhat.com> (raw)
In-Reply-To: <bb4c43a9-455d-aaba-37f4-a6874eb5ac51@arm.com>
On 11/12/20 09:49, Ard Biesheuvel wrote:
> On 11/9/20 2:05 PM, Jiahui Cen wrote:
>> Changes with v1
>> v1->v2:
>> Separated into four patches.
>> Factor the same logic parts into a new library.
>>
>> v1: https://edk2.groups.io/g/devel/topic/72723351#56901
>> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=3059
>> QEMU:
>> https://lore.kernel.org/qemu-devel/20201103120157.2286-1-cenjiahui@huawei.com/
>>
>>
>> This patch series adds support for extra pci roots for ARM.
>>
>
> Why?
I don't know Jiahui Cen's particular reasons; on x86, pxb-pcie is useful
for associating PCIe hierarchies with particular NUMA nodes. See
"docs/pci_expander_bridge.txt" in the QEMU tree.
Also, in Jiahui Cen's QEMU blurb linked above, the following is included:
> Currently pxb-pcie is not supported by arm,
> the reason for it is pxb-pcie is not described in DSDT table
> and only one main host bridge is described in acpi tables,
> which means it is not impossible to present different io numas
> for different devices.
So I guess this work aims to extend the same PCI(e)<->NUMA association
feature, from x86 to ARM.
Thanks,
Laszlo
next prev parent reply other threads:[~2020-11-13 19:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 13:05 [PATCH v2 0/4] Add extra pci roots support for Arm Jiahui Cen
2020-11-09 13:05 ` [PATCH v2 1/4] OvmfPkg: Extract functions form PciHostBridgeLib Jiahui Cen
2020-11-11 16:45 ` Laszlo Ersek
2020-11-12 3:21 ` Jiahui Cen
2020-11-09 13:05 ` [PATCH v2 2/4] ArmVirtPkg: Use extracted PciHostBridgeUtilityLib Jiahui Cen
2020-11-11 17:27 ` Laszlo Ersek
2020-11-12 3:30 ` [edk2-devel] " Jiahui Cen
2020-11-09 13:05 ` [PATCH v2 3/4] OvmfPkg: Extract functions of extra pci roots Jiahui Cen
2020-11-09 13:05 ` [PATCH v2 4/4] ArmVirtPkg: Support " Jiahui Cen
2020-11-11 14:33 ` [PATCH v2 0/4] Add extra pci roots support for Arm Laszlo Ersek
2020-11-12 3:20 ` [edk2-devel] " Jiahui Cen
2020-12-04 6:48 ` Jiahui Cen
2020-12-04 15:08 ` Laszlo Ersek
2020-12-11 10:57 ` Ni, Ray
2020-12-15 12:52 ` Jiahui Cen
2020-12-17 13:23 ` Laszlo Ersek
2020-12-17 13:37 ` Ard Biesheuvel
2020-12-17 14:42 ` Jonathan Cameron
2020-12-17 13:52 ` Jiahui Cen
2020-11-12 8:49 ` Ard Biesheuvel
2020-11-13 19:44 ` Laszlo Ersek [this message]
2020-11-16 1:33 ` [edk2-devel] " Jiahui Cen
-- strict thread matches above, loose matches on Subject: below --
2020-11-07 7:40 Jiahui Cen
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=286c4d14-82f4-6238-2fb1-15e6072fad07@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