From: Igor Mammedov <imammedo@redhat.com>
To: isaku.yamahata@gmail.com
Cc: isaku.yamahata@intel.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [PATCH v4 07/10] hw/i386: declare ACPI mother board resource for MMCONFIG region
Date: Tue, 16 Feb 2021 23:32:25 +0100 [thread overview]
Message-ID: <20210216233225.78a438ea@redhat.com> (raw)
In-Reply-To: <c7a950f33bba2fd1dc70ac825fdd64a6f40be184.1613436967.git.isaku.yamahata@intel.com>
On Mon, 15 Feb 2021 17:04:12 -0800
isaku.yamahata@gmail.com wrote:
> From: Isaku Yamahata <isaku.yamahata@intel.com>
>
> Declare PNP0C01 device to reserve MMCONFIG region to conform to the
> spec better and play nice with guest BIOSes/OSes.
>
> According to PCI Firmware Specification[0], MMCONFIG region must be
> reserved by declaring a motherboard resource. It's optional to reserve
> the region in memory map by Int 15 E820h or EFIGetMemoryMap.
> Guest Linux checks if the MMCFG region is reserved by bios memory map
> or ACPI resource. If it's not reserved, Linux falls back to legacy PCI
> configuration access.
>
> TDVF [1] [2] doesn't reserve MMCONFIG the region in memory map.
> On the other hand OVMF reserves it in memory map without declaring a
> motherboard resource. With memory map reservation, linux guest uses
> MMCONFIG region. However it doesn't comply to PCI Firmware
> specification.
>
> [0] PCI Firmware specification Revision 3.2
> 4.1.2 MCFG Table Description table 4-2 NOTE 2
> If the operating system does not natively comprehend reserving the
> MMCFG region, The MMCFG region must e reserved by firmware. ...
> For most systems, the mortheroard resource would appear at the root
> of the ACPI namespace (under \_SB)...
> The resource can optionally be returned in Int15 E820h or
> EFIGetMemoryMap as reserved memory but must always be reported
> through ACPI as a motherboard resource
>
> [1] TDX: Intel Trust Domain Extension
> https://software.intel.com/content/www/us/en/develop/articles/intel-trust-domain-extensions.html
> [2] TDX Virtual Firmware
> https://github.com/tianocore/edk2-staging/tree/TDVF
>
> The change to DSDT is as follows.
>
> @@ -68,32 +68,51 @@
>
> If ((CDW3 != Local0))
> {
> CDW1 |= 0x10
> }
>
> CDW3 = Local0
> }
> Else
> {
> CDW1 |= 0x04
> }
>
> Return (Arg3)
> }
> }
> +
> + Device (DRAC)
> + {
> + Name (_HID, "PNP0C01" /* System Board */) // _HID: Hardware ID
> + Name (RBUF, ResourceTemplate ()
> + {
> + DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, NonCacheable, ReadWrite,
> + 0x00000000, // Granularity
> + 0xB0000000, // Range Minimum
> + 0xB0000000, // Range Maximum
> + 0x00000000, // Translation Offset
> + 0x10000000, // Length
> + ,, , AddressRangeMemory, TypeStatic)
> + })
> + Method (_CRS, 0, Serialized) // _CRS: Current Resource Settings
> + {
> + Return (RBUF) /* \_SB_.DRAC.RBUF */
> + }
> + }
> }
>
> Scope (_SB)
> {
> Device (HPET)
> {
> Name (_HID, EisaId ("PNP0103") /* HPET System Timer */) // _HID: Hardware ID
> Name (_UID, Zero) // _UID: Unique ID
> OperationRegion (HPTM, SystemMemory, 0xFED00000, 0x0400)
> Field (HPTM, DWordAcc, Lock, Preserve)
> {
> VEND, 32,
> PRD, 32
> }
>
> Method (_STA, 0, NotSerialized) // _STA: Status
>
> Signed-off-by: Isaku Yamahata <isaku.yamahata@intel.com>
> ---
> hw/i386/acpi-build.c | 55 +++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 54 insertions(+), 1 deletion(-)
>
> diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
> index e3386ae674..30326f69b3 100644
> --- a/hw/i386/acpi-build.c
> +++ b/hw/i386/acpi-build.c
> @@ -1072,6 +1072,55 @@ static void build_q35_pci0_int(Aml *table)
> aml_append(table, sb_scope);
> }
>
> +static Aml *build_q35_dram_controller(AcpiMcfgInfo *mcfg)
> +{
> + Aml *dev;
> + Aml *rbuf;
> + Aml *resource_template;
> + Aml *rbuf_name;
> + Aml *crs;
> +
> + /* DRAM controller */
> + dev = aml_device("DRAC");
> + aml_append(dev, aml_name_decl("_HID", aml_string("PNP0C01")));
> +
> + resource_template = aml_resource_template();
> + if (mcfg->base + mcfg->size - 1 >= (1ULL << 32)) {
> + aml_append(resource_template,
> + aml_qword_memory(AML_POS_DECODE,
> + AML_MIN_FIXED,
> + AML_MAX_FIXED,
> + AML_NON_CACHEABLE,
> + AML_READ_WRITE,
> + 0x0000000000000000,
> + mcfg->base,
> + mcfg->base,
here ^^^
> + aml_append(resource_template,
> + aml_dword_memory(AML_POS_DECODE,
> + AML_MIN_FIXED,
> + AML_MAX_FIXED,
> + AML_NON_CACHEABLE,
> + AML_READ_WRITE,
> + 0x0000000000000000,
> + mcfg->base,
> + mcfg->base,
and here ^^^
please revert it to the way did it in v3,
I was wrong suggesting that for fixed address case.
> + 0x0000000000000000,
> + mcfg->size));
> + }
> + rbuf = aml_name_decl("RBUF", resource_template);
> + aml_append(dev, rbuf);
> +
> + crs = aml_method("_CRS", 0, AML_SERIALIZED);
> + rbuf_name = aml_name("RBUF");
> + aml_append(crs, aml_return(rbuf_name));
> + aml_append(dev, crs);
can be simpler if method is replaced with _CRS variable, i.e.:
aml_append(dev, aml_name_decl("_CRS", resource_template));
> +
> + return dev;
> +}
> +
> static void build_q35_isa_bridge(Aml *table)
> {
> Aml *dev;
> @@ -1218,6 +1267,7 @@ build_dsdt(GArray *table_data, BIOSLinker *linker,
> PCMachineClass *pcmc = PC_MACHINE_GET_CLASS(machine);
> X86MachineState *x86ms = X86_MACHINE(machine);
> AcpiMcfgInfo mcfg;
> + bool mcfg_valid = !!acpi_get_mcfg(&mcfg);
> uint32_t nr_mem = machine->ram_slots;
> int root_bus_limit = 0xFF;
> PCIBus *bus = NULL;
> @@ -1256,6 +1306,9 @@ build_dsdt(GArray *table_data, BIOSLinker *linker,
> aml_append(dev, aml_name_decl("_UID", aml_int(0)));
> aml_append(dev, build_q35_osc_method());
> aml_append(sb_scope, dev);
> + if (mcfg_valid) {
> + aml_append(sb_scope, build_q35_dram_controller(&mcfg));
> + }
>
> if (pm->smi_on_cpuhp) {
> /* reserve SMI block resources, IO ports 0xB2, 0xB3 */
> @@ -1386,7 +1439,7 @@ build_dsdt(GArray *table_data, BIOSLinker *linker,
> * the PCI0._CRS. Add mmconfig to the set so it will be excluded
> * too.
> */
> - if (acpi_get_mcfg(&mcfg)) {
> + if (mcfg_valid) {
> crs_range_insert(crs_range_set.mem_ranges,
> mcfg.base, mcfg.base + mcfg.size - 1);
> }
next prev parent reply other threads:[~2021-02-16 22:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 1:04 [PATCH v4 00/10] ACPI related fixes to comform the spec better isaku.yamahata
2021-02-16 1:04 ` [PATCH v4 01/10] checkpatch: don't emit warning on newly created acpi data files isaku.yamahata
2021-02-16 1:04 ` [PATCH v4 02/10] qtest: update tests/qtest/bios-tables-test-allowed-diff.h isaku.yamahata
2021-02-16 1:04 ` [PATCH v4 03/10] ich9, piix4: add properoty, smm-compat, to keep compatibility of SMM isaku.yamahata
2021-02-16 22:21 ` Igor Mammedov
2021-02-16 1:04 ` [PATCH v4 04/10] acpi/core: always set SCI_EN when SMM isn't supported isaku.yamahata
2021-02-16 22:22 ` Igor Mammedov
2021-02-16 1:04 ` [PATCH v4 05/10] acpi: set fadt.smi_cmd to zero when SMM is not supported isaku.yamahata
2021-02-16 1:04 ` [PATCH v4 06/10] acpi: add test case for smm unsupported -machine smm=off isaku.yamahata
2021-02-16 1:04 ` [PATCH v4 07/10] hw/i386: declare ACPI mother board resource for MMCONFIG region isaku.yamahata
2021-02-16 22:32 ` Igor Mammedov [this message]
2021-02-16 1:04 ` [PATCH v4 08/10] i386: acpi: Don't build HPET ACPI entry if HPET is disabled isaku.yamahata
2021-02-16 1:04 ` [PATCH v4 09/10] acpi: add test case for -no-hpet isaku.yamahata
2021-02-16 1:04 ` [PATCH v4 10/10] qtest/acpi/bios-tables-test: update acpi tables isaku.yamahata
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=20210216233225.78a438ea@redhat.com \
--to=imammedo@redhat.com \
--cc=isaku.yamahata@gmail.com \
--cc=isaku.yamahata@intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.