qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Ying Fang <fangying1@huawei.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	lersek@redhat.com, QEMU Developers <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	"wangzhigang17@huawei.com" <wangzhigang17@huawei.com>,
	philmd@redhat.com
Subject: Re: Question on UEFI ACPI tables setup and probing on arm64
Date: Tue, 3 Nov 2020 13:39:13 +0100	[thread overview]
Message-ID: <20201103133913.1fee3337@redhat.com> (raw)
In-Reply-To: <ee3b7fdf-f6ba-cafc-5b44-42b0bcda01c5@huawei.com>

On Fri, 30 Oct 2020 10:50:01 +0800
Ying Fang <fangying1@huawei.com> wrote:

> Hi,
> 
> I have a question on UEFI/ACPI tables setup and probing on arm64 platform.

CCing Laszlo,
who might know how it's implemented.
 
> Currently on arm64 platform guest can be booted with both fdt and ACPI
> supported. If ACPI is enabled, [1] says the only defined method for
> passing ACPI tables to the kernel is via the UEFI system configuration
> table. So AFAIK, ACPI Should be dependent on UEFI.
> 
> What's more [2] says UEFI kernel support on the ARM architectures
> is only available through a *stub*. The stub populates the FDT /chosen
> node with some UEFI parameters describing the UEFI location info.
> 
> So i dump /sys/firmware/fdt from the guest, it does have something like:
> 
> /dts-v1/;
> 
> / {
> 	#size-cells = <0x02>;
> 	#address-cells = <0x02>;
> 
> 	chosen {
> 		linux,uefi-mmap-desc-ver = <0x01>;
> 		linux,uefi-mmap-desc-size = <0x30>;
> 		linux,uefi-mmap-size = <0x810>;
> 		linux,uefi-mmap-start = <0x04 0x3c0ce018>;
> 		linux,uefi-system-table = <0x04 0x3f8b0018>;
> 		bootargs = "BOOT_IMAGE=/vmlinuz-4.19.90-2003.4.0.0036.oe1.aarch64 
> root=/dev/mapper/openeuler-root ro rd.lvm.lv=openeuler/root 
> rd.lvm.lv=openeuler/swap video=VGA-1:640x480-32@60me 
> smmu.bypassdev=0x1000:0x17 smmu.bypassdev=0x1000:0x15 
> crashkernel=1024M,high video=efifb:off video=VGA-1:640x480-32@60me";
> 		linux,initrd-end = <0x04 0x3a85a5da>;
> 		linux,initrd-start = <0x04 0x392f2000>;
> 	};
> };
> 
> But the question is that I did not see any code adding the uefi
> in fdt chosen node in *arm_load_dtb* or anywhere else.
> Qemu only maps the OVMF binary file into a pflash device.
> So I'm really confused on how UEFI information is provided to
> guest by qemu. Does anybody know of the details about it ?
> 
> [1] https://www.kernel.org/doc/html/latest/arm64/arm-acpi.html
> [2] https://www.kernel.org/doc/Documentation/arm/uefi.rst
> 
> Thanks.
> Ying
> 



  reply	other threads:[~2020-11-03 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30  2:50 Question on UEFI ACPI tables setup and probing on arm64 Ying Fang
2020-11-03 12:39 ` Igor Mammedov [this message]
2020-11-04 21:46   ` Laszlo Ersek
2020-11-04 21:57     ` Ard Biesheuvel
2020-11-05  4:30     ` Ying Fang
2020-11-06 17:09       ` Laszlo Ersek
2020-11-10  1:42         ` Ying Fang

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=20201103133913.1fee3337@redhat.com \
    --to=imammedo@redhat.com \
    --cc=fangying1@huawei.com \
    --cc=lersek@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wangzhigang17@huawei.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).