From: Igor Mammedov <imammedo@redhat.com>
To: Sunil V L <sunilvl@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bmeng.cn@gmail.com>, Weiwei Li <liwei1518@gmail.com>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Ani Sinha <anisinha@redhat.com>
Subject: Re: [PATCH v2 4/9] acpi/gpex: Create PCI link devices outside PCI root bridge
Date: Thu, 11 Jul 2024 15:43:33 +0200 [thread overview]
Message-ID: <20240711154333.262e0bda@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <20240708114741.3499585-5-sunilvl@ventanamicro.com>
On Mon, 8 Jul 2024 17:17:36 +0530
Sunil V L <sunilvl@ventanamicro.com> wrote:
> Currently, PCI link devices (PNP0C0F) are always created within the
> scope of the PCI root bridge. However, RISC-V needs these link devices
> to be created outside to ensure the probing order in the OS. This
> matches the example given in the ACPI specification [1] as well. Hence,
> create these link devices directly under _SB instead of under the PCI
> root bridge.
>
> To keep these link device names unique for multiple PCI bridges, change
> the device name from GSIx to LXXY format where XX is the PCI bus number
> and Y is the INTx.
>
> GPEX is currently used by riscv, aarch64/virt and x86/microvm machines.
> So, this change will alter the DSDT for those systems.
>
> [1] - ACPI 5.1: 6.2.13.1 Example: Using _PRT to Describe PCI IRQ Routing
>
> Signed-off-by: Sunil V L <sunilvl@ventanamicro.com>
> ---
> hw/pci-host/gpex-acpi.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/hw/pci-host/gpex-acpi.c b/hw/pci-host/gpex-acpi.c
> index f69413ea2c..a93b55c991 100644
> --- a/hw/pci-host/gpex-acpi.c
> +++ b/hw/pci-host/gpex-acpi.c
> @@ -7,7 +7,8 @@
> #include "hw/pci/pcie_host.h"
> #include "hw/acpi/cxl.h"
>
> -static void acpi_dsdt_add_pci_route_table(Aml *dev, uint32_t irq)
> +static void acpi_dsdt_add_pci_route_table(Aml *dev, uint32_t irq,
> + Aml *scope, uint8_t bus_num)
> {
> Aml *method, *crs;
> int i, slot_no;
> @@ -20,7 +21,7 @@ static void acpi_dsdt_add_pci_route_table(Aml *dev, uint32_t irq)
> Aml *pkg = aml_package(4);
> aml_append(pkg, aml_int((slot_no << 16) | 0xFFFF));
> aml_append(pkg, aml_int(i));
> - aml_append(pkg, aml_name("GSI%d", gsi));
> + aml_append(pkg, aml_name("L%.02X%d", bus_num, gsi));
instead of mixing hex and decimal here, make gsi hex as well to be consistent?
> aml_append(pkg, aml_int(0));
> aml_append(rt_pkg, pkg);
> }
> @@ -30,7 +31,7 @@ static void acpi_dsdt_add_pci_route_table(Aml *dev, uint32_t irq)
> /* Create GSI link device */
> for (i = 0; i < PCI_NUM_PINS; i++) {
> uint32_t irqs = irq + i;
> - Aml *dev_gsi = aml_device("GSI%d", i);
> + Aml *dev_gsi = aml_device("L%.02X%d", bus_num, i);
ditto
> aml_append(dev_gsi, aml_name_decl("_HID", aml_string("PNP0C0F")));
> aml_append(dev_gsi, aml_name_decl("_UID", aml_int(i)));
> crs = aml_resource_template();
> @@ -45,7 +46,7 @@ static void acpi_dsdt_add_pci_route_table(Aml *dev, uint32_t irq)
> aml_append(dev_gsi, aml_name_decl("_CRS", crs));
> method = aml_method("_SRS", 1, AML_NOTSERIALIZED);
> aml_append(dev_gsi, method);
> - aml_append(dev, dev_gsi);
> + aml_append(scope, dev_gsi);
> }
> }
>
> @@ -174,7 +175,7 @@ void acpi_dsdt_add_gpex(Aml *scope, struct GPEXConfig *cfg)
> aml_append(dev, aml_name_decl("_PXM", aml_int(numa_node)));
> }
>
> - acpi_dsdt_add_pci_route_table(dev, cfg->irq);
> + acpi_dsdt_add_pci_route_table(dev, cfg->irq, scope, bus_num);
>
> /*
> * Resources defined for PXBs are composed of the following parts:
> @@ -205,7 +206,7 @@ void acpi_dsdt_add_gpex(Aml *scope, struct GPEXConfig *cfg)
> aml_append(dev, aml_name_decl("_STR", aml_unicode("PCIe 0 Device")));
> aml_append(dev, aml_name_decl("_CCA", aml_int(1)));
>
> - acpi_dsdt_add_pci_route_table(dev, cfg->irq);
> + acpi_dsdt_add_pci_route_table(dev, cfg->irq, scope, 0);
>
> method = aml_method("_CBA", 0, AML_NOTSERIALIZED);
> aml_append(method, aml_return(aml_int(cfg->ecam.base)));
next prev parent reply other threads:[~2024-07-11 13:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 11:47 [PATCH v2 0/9] RISC-V: ACPI: Namespace updates Sunil V L
2024-07-08 11:47 ` [PATCH v2 1/9] hw/riscv/virt-acpi-build.c: Add namespace devices for PLIC and APLIC Sunil V L
2024-07-11 13:17 ` Igor Mammedov
2024-07-11 13:21 ` Igor Mammedov
2024-07-08 11:47 ` [PATCH v2 2/9] hw/riscv/virt-acpi-build.c: Update the HID of RISC-V UART Sunil V L
2024-07-11 13:25 ` Igor Mammedov
2024-07-11 14:41 ` Michael S. Tsirkin
2024-07-12 5:07 ` Sunil V L
2024-07-08 11:47 ` [PATCH v2 3/9] tests/acpi: Allow DSDT acpi table changes for aarch64 Sunil V L
2024-07-11 13:53 ` Igor Mammedov
2024-07-08 11:47 ` [PATCH v2 4/9] acpi/gpex: Create PCI link devices outside PCI root bridge Sunil V L
2024-07-11 13:43 ` Igor Mammedov [this message]
2024-07-08 11:47 ` [PATCH v2 5/9] tests/acpi: update expected DSDT blob for aarch64 and microvm Sunil V L
2024-07-08 11:47 ` [PATCH v2 6/9] tests/qtest/bios-tables-test.c: Remove the fall back path Sunil V L
2024-07-10 0:54 ` Alistair Francis
2024-07-11 13:53 ` Igor Mammedov
2024-07-08 11:47 ` [PATCH v2 7/9] tests/acpi: Add empty ACPI data files for RISC-V Sunil V L
2024-07-08 11:47 ` [PATCH v2 8/9] tests/qtest/bios-tables-test.c: Enable basic testing " Sunil V L
2024-07-08 11:47 ` [PATCH v2 9/9] tests/acpi: Add expected ACPI AML files " Sunil V L
2024-07-12 12:43 ` [PATCH v2 0/9] RISC-V: ACPI: Namespace updates Igor Mammedov
2024-07-12 12:51 ` Daniel P. Berrangé
2024-07-12 13:50 ` Igor Mammedov
2024-07-14 7:46 ` Michael S. Tsirkin
2024-07-15 12:43 ` Igor Mammedov
2024-07-16 12:26 ` Sunil V L
2024-07-16 14:28 ` Igor Mammedov
2024-07-16 14:33 ` Igor Mammedov
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-all 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=20240711154333.262e0bda@imammedo.users.ipa.redhat.com \
--to=imammedo@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=anisinha@redhat.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=mst@redhat.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sunilvl@ventanamicro.com \
--cc=zhiwei_liu@linux.alibaba.com \
/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;
as well as URLs for NNTP newsgroup(s).