From: Laszlo Ersek <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH v2 11/12] ArmVirtPkg/PlatformHasAcpiDtDxe: don't expose DT if QEMU provides ACPI
Date: Fri, 17 Mar 2017 22:25:45 +0100 [thread overview]
Message-ID: <e0dffc7f-2f20-8732-83e6-c708f251d995@redhat.com> (raw)
In-Reply-To: <CAKv+Gu8zc2ozMnQCdBWmn1G-uifjTs4YWnss89N68p20KopsGA@mail.gmail.com>
On 03/17/17 22:10, Ard Biesheuvel wrote:
> On 17 March 2017 at 20:47, Laszlo Ersek <lersek@redhat.com> wrote:
>> This will let QEMU's "-no-acpi" option exclusively expose DT vs. ACPI to
>> the guest. Showing both is never needed (it is actually detrimental to the
>> adoption of standards, such as SBSA / SBBR).
>>
>> * Without "-no-acpi", the firmware logs (from PlatformHasAcpiDtDxe)
>>
>>> Found FwCfg @ 0x9020008/0x9020000
>>> Found FwCfg DMA @ 0x9020010
>>> InstallProtocolInterface: [EdkiiPlatformHasAcpiProtocol] 0
>>
>> plus the usual messages. Later the guest kernel logs
>>
>>> [ 0.000000] efi: SMBIOS 3.0=0x13bdb0000 ACPI 2.0=0x138440000
>
> Why is there no MEMATTR table in this case? Or was it omitted for brevity?
I don't have the slightest clue. What is the MEMATTR table?
... Hm, grepping the kernel, it's apparently the memory attributes
table. You added it in the following kernel commit:
a604af075a32 ("efi: Add support for the EFI_MEMORY_ATTRIBUTES_TABLE
config table", 2016-04-25)
and it is part of release v4.7.
Ah, I understand now. I used two kernels (two guests) for testing this,
namely "4.7.7-200.fc24.aarch64" and "4.5.0-15.el7.aarch64".
And, from the logs I collected, the "-no-acpi" log belongs to the Fedora
kernel, which has your MEMATTR patch; while the log without "-no-acpi"
(above) belongs to the RHEL-7.3 kernel, which does *not* have your
MEMATTR patch.
I've now removed "-no-acpi" from the Fedora 24 guest's config, and
repeated the test. It prints:
[ 0.000000] efi: SMBIOS 3.0=0x13bdb0000 ACPI 2.0=0x138440000
MEMATTR=0x13a689018
If you wish (and I don't have to submit a v3 for any other reason), I
can refresh the above line in the commit message.
Thanks!
Laszlo
>
>>
>> before it lists the ACPI tables one by one.
>>
>> * With "-no-acpi", the firmware logs:
>>
>>> PlatformHasAcpiDtDxe | Found FwCfg @ 0x9020008/0x9020000
>>> PlatformHasAcpiDtDxe | Found FwCfg DMA @ 0x9020010
>>> PlatformHasAcpiDtDxe | InstallProtocolInterface:
>>> PlatformHasAcpiDtDxe | [EdkiiPlatformHasDeviceTreeProtocol] 0
>>> FdtClientDxe | OnPlatformHasDeviceTree: exposing DTB @
>>> FdtClientDxe | 0x13FFBF000 to OS
>>> ...
>>> DXE_CORE | Driver [AcpiTableDxe] was discovered but not
>>> DXE_CORE | loaded!!
>>> DXE_CORE | Driver [QemuFwCfgAcpiPlatform] was discovered but
>>> DXE_CORE | not loaded!!
>>> ...
>>> RamDiskDxe | RamDiskAcpiCheck: Cannot locate the EFI ACPI
>>> RamDiskDxe | Table Protocol, unable to publish RAM disks to
>>> RamDiskDxe | NFIT.
>>
>> (BootGraphicsResourceTableDxe's ReadyToBoot callback --
>> InstallBootGraphicsResourceTable() -- handles the lack of
>> EFI_ACPI_TABLE_PROTOCOL silently.) Later the guest kernel logs
>>
>>> [ 0.000000] efi: SMBIOS 3.0=0x13bdb0000 MEMATTR=0x138b3c018
>>
>> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> Cc: Leif Lindholm <leif.lindholm@linaro.org>
>> Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1430262
>> Contributed-under: TianoCore Contribution Agreement 1.0
>> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>> ---
>> ArmVirtPkg/PlatformHasAcpiDtDxe/PlatformHasAcpiDtDxe.inf | 6 +--
>> ArmVirtPkg/PlatformHasAcpiDtDxe/PlatformHasAcpiDtDxe.c | 45 ++++++++++++--------
>> 2 files changed, 29 insertions(+), 22 deletions(-)
>>
>> diff --git a/ArmVirtPkg/PlatformHasAcpiDtDxe/PlatformHasAcpiDtDxe.inf b/ArmVirtPkg/PlatformHasAcpiDtDxe/PlatformHasAcpiDtDxe.inf
>> index 7724cf215dda..95a56a10bb5c 100644
>> --- a/ArmVirtPkg/PlatformHasAcpiDtDxe/PlatformHasAcpiDtDxe.inf
>> +++ b/ArmVirtPkg/PlatformHasAcpiDtDxe/PlatformHasAcpiDtDxe.inf
>> @@ -28,11 +28,12 @@ [Packages]
>> ArmPkg/ArmPkg.dec
>> ArmVirtPkg/ArmVirtPkg.dec
>> MdePkg/MdePkg.dec
>> + OvmfPkg/OvmfPkg.dec
>>
>> [LibraryClasses]
>> BaseLib
>> DebugLib
>> - PcdLib
>> + QemuFwCfgLib
>> UefiBootServicesTableLib
>> UefiDriverEntryPoint
>>
>> @@ -40,8 +41,5 @@ [Protocols]
>> gEdkiiPlatformHasAcpiProtocolGuid ## SOMETIMES_PRODUCES
>> gEdkiiPlatformHasDeviceTreeProtocolGuid ## SOMETIMES_PRODUCES
>>
>> -[FeaturePcd]
>> - gArmVirtTokenSpaceGuid.PcdPureAcpiBoot ## CONSUMES
>> -
>> [Depex]
>> TRUE
>> diff --git a/ArmVirtPkg/PlatformHasAcpiDtDxe/PlatformHasAcpiDtDxe.c b/ArmVirtPkg/PlatformHasAcpiDtDxe/PlatformHasAcpiDtDxe.c
>> index 8681f813a6b5..46f96401632c 100644
>> --- a/ArmVirtPkg/PlatformHasAcpiDtDxe/PlatformHasAcpiDtDxe.c
>> +++ b/ArmVirtPkg/PlatformHasAcpiDtDxe/PlatformHasAcpiDtDxe.c
>> @@ -15,7 +15,7 @@
>>
>> #include <Library/BaseLib.h>
>> #include <Library/DebugLib.h>
>> -#include <Library/PcdLib.h>
>> +#include <Library/QemuFwCfgLib.h>
>> #include <Library/UefiBootServicesTableLib.h>
>> #include <Protocol/PlatformHasAcpi.h>
>> #include <Protocol/PlatformHasDeviceTree.h>
>> @@ -27,18 +27,27 @@ PlatformHasAcpiDt (
>> IN EFI_SYSTEM_TABLE *SystemTable
>> )
>> {
>> - EFI_STATUS Status;
>> -
>> - Status = EFI_SUCCESS;
>> + EFI_STATUS Status;
>> + FIRMWARE_CONFIG_ITEM FwCfgItem;
>> + UINTN FwCfgSize;
>>
>> //
>> // If we fail to install any of the necessary protocols below, the OS will be
>> // unbootable anyway (due to lacking hardware description), so tolerate no
>> // errors here.
>> //
>> - // Always make ACPI available on 64-bit systems.
>> - //
>> - if (MAX_UINTN == MAX_UINT64) {
>> + if (MAX_UINTN == MAX_UINT64 &&
>> + !EFI_ERROR (
>> + QemuFwCfgFindFile (
>> + "etc/table-loader",
>> + &FwCfgItem,
>> + &FwCfgSize
>> + )
>> + )) {
>> + //
>> + // Only make ACPI available on 64-bit systems, and only if QEMU generates
>> + // (a subset of) the ACPI tables.
>> + //
>> Status = gBS->InstallProtocolInterface (
>> &ImageHandle,
>> &gEdkiiPlatformHasAcpiProtocolGuid,
>> @@ -48,21 +57,21 @@ PlatformHasAcpiDt (
>> if (EFI_ERROR (Status)) {
>> goto Failed;
>> }
>> +
>> + return Status;
>> }
>>
>> //
>> - // Expose the Device Tree unless PcdPureAcpiBoot is set.
>> + // Expose the Device Tree otherwise.
>> //
>> - if (!FeaturePcdGet (PcdPureAcpiBoot)) {
>> - Status = gBS->InstallProtocolInterface (
>> - &ImageHandle,
>> - &gEdkiiPlatformHasDeviceTreeProtocolGuid,
>> - EFI_NATIVE_INTERFACE,
>> - NULL
>> - );
>> - if (EFI_ERROR (Status)) {
>> - goto Failed;
>> - }
>> + Status = gBS->InstallProtocolInterface (
>> + &ImageHandle,
>> + &gEdkiiPlatformHasDeviceTreeProtocolGuid,
>> + EFI_NATIVE_INTERFACE,
>> + NULL
>> + );
>> + if (EFI_ERROR (Status)) {
>> + goto Failed;
>> }
>>
>> return Status;
>> --
>> 2.9.3
>>
>>
next prev parent reply other threads:[~2017-03-17 21:25 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 20:47 [PATCH v2 00/12] ArmVirtPkg: don't forward the DT to the OS if QEMU provides ACPI Laszlo Ersek
2017-03-17 20:47 ` [PATCH v2 01/12] Revert "ArmVirtPkg/FdtClientDxe: make DT table installation !ACPI dependent" Laszlo Ersek
2017-03-22 14:12 ` Ard Biesheuvel
2017-03-17 20:47 ` [PATCH v2 02/12] Revert "ArmVirtPkg/FdtClientDxe: install DT configuration table at ReadyToBoot" Laszlo Ersek
2017-03-22 14:12 ` Ard Biesheuvel
2017-03-17 20:47 ` [PATCH v2 03/12] MdeModulePkg/RamDiskDxe: fix C string literal catenation in info messages Laszlo Ersek
2017-03-20 2:16 ` Zeng, Star
2017-03-20 2:26 ` Tian, Feng
2017-03-20 2:34 ` Wu, Hao A
2017-03-20 9:46 ` Laszlo Ersek
2017-03-20 9:57 ` Zeng, Star
2017-03-20 10:10 ` Laszlo Ersek
2017-03-17 20:47 ` [PATCH v2 04/12] ArmVirtPkg/XenAcpiPlatformDxe: don't cast UINT64 to pointer directly Laszlo Ersek
2017-03-22 14:13 ` Ard Biesheuvel
2017-03-17 20:47 ` [PATCH v2 05/12] ArmPkg: introduce EDKII Platform Has ACPI Protocol, and plug-in library Laszlo Ersek
2017-03-18 15:00 ` Leif Lindholm
2017-03-20 9:01 ` Laszlo Ersek
2017-03-20 11:59 ` Leif Lindholm
2017-03-22 15:01 ` Laszlo Ersek
2017-03-23 1:41 ` Zeng, Star
2017-03-23 9:09 ` Ard Biesheuvel
2017-03-24 3:44 ` Zeng, Star
2017-03-24 7:15 ` Ard Biesheuvel
2017-03-24 17:10 ` Laszlo Ersek
2017-03-24 17:11 ` Ard Biesheuvel
2017-03-24 17:09 ` Laszlo Ersek
2017-03-27 2:42 ` Gao, Liming
2017-03-27 7:00 ` Ard Biesheuvel
2017-03-27 17:31 ` Laszlo Ersek
2017-03-27 17:45 ` Ard Biesheuvel
2017-03-28 5:25 ` Gao, Liming
2017-03-28 7:49 ` Laszlo Ersek
2017-03-29 9:49 ` Gao, Liming
2017-03-29 13:03 ` Laszlo Ersek
2017-03-20 2:23 ` Zeng, Star
2017-03-20 9:17 ` Laszlo Ersek
2017-03-20 9:57 ` Zeng, Star
2017-03-21 2:27 ` Zeng, Star
2017-03-21 7:10 ` Ard Biesheuvel
2017-03-21 8:43 ` Ard Biesheuvel
2017-03-21 9:02 ` Laszlo Ersek
2017-03-21 18:00 ` Laszlo Ersek
2017-03-22 14:12 ` Ard Biesheuvel
2017-03-21 8:37 ` Laszlo Ersek
2017-03-21 8:41 ` Zeng, Star
2017-03-21 9:05 ` Laszlo Ersek
2017-03-22 16:45 ` Laszlo Ersek
2017-03-17 20:47 ` [PATCH v2 06/12] ArmPkg: introduce EDKII Platform Has Device Tree Protocol Laszlo Ersek
2017-03-18 15:06 ` Leif Lindholm
2017-03-20 9:03 ` Laszlo Ersek
2017-03-17 20:47 ` [PATCH v2 07/12] ArmVirtPkg: add PlatformHasAcpiDtDxe Laszlo Ersek
2017-03-22 14:14 ` Ard Biesheuvel
2017-03-17 20:47 ` [PATCH v2 08/12] ArmVirtPkg: add XenPlatformHasAcpiDtDxe Laszlo Ersek
2017-03-22 14:15 ` Ard Biesheuvel
2017-03-17 20:47 ` [PATCH v2 09/12] ArmVirtPkg: enable AcpiTableDxe and EFI_ACPI_TABLE_PROTOCOL dynamically Laszlo Ersek
2017-03-22 14:16 ` Ard Biesheuvel
2017-03-22 14:54 ` Laszlo Ersek
2017-03-22 15:05 ` Ard Biesheuvel
2017-03-17 20:47 ` [PATCH v2 10/12] ArmVirtPkg/FdtClientDxe: install DT as sysconfig table in protocol notify Laszlo Ersek
2017-03-22 14:18 ` Ard Biesheuvel
2017-03-17 20:47 ` [PATCH v2 11/12] ArmVirtPkg/PlatformHasAcpiDtDxe: don't expose DT if QEMU provides ACPI Laszlo Ersek
2017-03-17 21:10 ` Ard Biesheuvel
2017-03-17 21:25 ` Laszlo Ersek [this message]
2017-03-17 21:27 ` Ard Biesheuvel
2017-03-22 14:18 ` Ard Biesheuvel
2017-03-17 20:47 ` [PATCH v2 12/12] ArmVirtPkg: remove PURE_ACPI_BOOT_ENABLE and PcdPureAcpiBoot Laszlo Ersek
2017-03-22 14:19 ` Ard Biesheuvel
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=e0dffc7f-2f20-8732-83e6-c708f251d995@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