From: Julien Grall <julien.grall@citrix.com>
To: Shannon Zhao <shannon.zhao@linaro.org>,
xen-devel@lists.xen.org,
Christoffer Dall <christoffer.dall@linaro.org>,
Ian Campbell <ian.campbell@citrix.com>,
stefano.stabellini@eu.citrix.com,
Stefano Stabellini <stefano.stabellini@citrix.com>,
JBeulich@suse.com, Parth Dixit <parth.dixit@linaro.org>,
andrew@fubar.geek.nz, boris.ostrovsky@oracle.com,
david.vrabel@citrix.com
Cc: Hangaohuai <hangaohuai@huawei.com>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
Shannon Zhao <zhaoshenglong@huawei.com>
Subject: Re: Design doc of adding ACPI support for arm64 on Xen - version 3
Date: Mon, 17 Aug 2015 09:10:48 -0700 [thread overview]
Message-ID: <55D20788.9050503@citrix.com> (raw)
In-Reply-To: <55D1DB2D.6050807@linaro.org>
Hi,
On 17/08/2015 06:01, Shannon Zhao wrote:
>
>
> On 2015/8/14 23:17, Julien Grall wrote:
>> On 14/08/15 15:59, Shannon Zhao wrote:
>>> 2. Create minimal DT to pass required information to Dom0
>>> ----------------------------------------------------------
>>> The minimal DT mainly passes Dom0 bootargs, address and size of initrd
>>> (if available), address and size of uefi system table, address and size
>>> of uefi memory table, uefi-mmap-desc-size and uefi-mmap-desc-ver.
>>>
>>> An example of the minimal DT:
>>> / {
>>> #address-cells = <2>;
>>> #size-cells = <1>;
>>> chosen {
>>> bootargs = "kernel=Image console=hvc0 earlycon=pl011,0x1c090000
>>> root=/dev/vda2 rw rootfstype=ext4 init=/bin/sh acpi=force";
>>> linux,initrd-start = <0xXXXXXXXX>;
>>> linux,initrd-end = <0xXXXXXXXX>;
>>> linux,uefi-system-table = <0xXXXXXXXX>;
>>> linux,uefi-mmap-start = <0xXXXXXXXX>;
>>> linux,uefi-mmap-size = <0xXXXXXXXX>;
>>> linux,uefi-mmap-desc-size = <0xXXXXXXXX>;
>>> linux,uefi-mmap-desc-ver = <0xXXXXXXXX>;
>>> };
>>> };
>>>
>>> For details loook at
>>> https://github.com/torvalds/linux/blob/master/Documentation/arm/uefi.txt
>>
>> I would have expect a summary on the discussion we had on the previous
>> thread [1].
>>
>> Note that "linux,initrd-*" are well defined given that Xen, U-boot and
>> other bootloaders are using them. And IIRC, it's Linux specific.
>>
>> Although, "linux,uefi-*" are not well defined (only used internally by
>> Linux betwen the EFI stub and the kernel) and we expect other OS to use
>> them in the future.
>>
>> So I would prefer to the "linux," dropped for them.
>>
>
> Yes, I think it's good to drop the "linux," too. But if we drop the
> linux, would it impact the linux kernel booting with UEFI? And why we
> don't do it to Xen since Xen still uses "linux,"?
I don't understand your second question.
For the first question, as we discussed in several mail, the property
"linux,uefi-*" are only used internally between the stub and Linux. The
sub is compiled in the kernel so there is no issue to change the property.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-08-17 16:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 14:59 Design doc of adding ACPI support for arm64 on Xen - version 3 Shannon Zhao
2015-08-14 15:17 ` Julien Grall
2015-08-17 13:01 ` Shannon Zhao
2015-08-17 16:10 ` Julien Grall [this message]
2015-08-18 3:19 ` Shannon Zhao
2015-08-18 6:36 ` Julien Grall
2015-08-18 7:23 ` Shannon Zhao
2015-08-18 16:13 ` Julien Grall
2015-08-14 15:59 ` Konrad Rzeszutek Wilk
2015-08-17 15:33 ` Jan Beulich
2015-08-17 16:19 ` Julien Grall
2015-08-18 5:10 ` Jan Beulich
2015-08-18 6:43 ` Julien Grall
2015-08-18 7:01 ` Jan Beulich
2015-08-18 7:46 ` Shannon Zhao
2015-08-18 19:01 ` Julien Grall
2015-08-18 3:41 ` Shannon Zhao
2015-08-18 5:14 ` Jan Beulich
2015-08-18 7:35 ` Shannon Zhao
2015-08-18 8:15 ` Jan Beulich
2015-08-18 8:21 ` Shannon Zhao
2015-08-18 9:11 ` Jan Beulich
2015-08-18 9:34 ` Shannon Zhao
2015-08-18 19:00 ` Julien Grall
2015-09-02 11:43 ` Ian Campbell
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=55D20788.9050503@citrix.com \
--to=julien.grall@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew@fubar.geek.nz \
--cc=boris.ostrovsky@oracle.com \
--cc=christoffer.dall@linaro.org \
--cc=david.vrabel@citrix.com \
--cc=hangaohuai@huawei.com \
--cc=ian.campbell@citrix.com \
--cc=parth.dixit@linaro.org \
--cc=peter.huangpeng@huawei.com \
--cc=shannon.zhao@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=zhaoshenglong@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).