xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Shannon Zhao <zhaoshenglong@huawei.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	Daniel Kiper <daniel.kiper@oracle.com>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Shannon Zhao <shannon.zhao@linaro.org>,
	Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: About runtime service for Xen on ARM
Date: Tue, 25 Aug 2015 20:24:08 -0700	[thread overview]
Message-ID: <55DD3158.3080003@citrix.com> (raw)
In-Reply-To: <55D5733B.4050804@huawei.com>



On 19/08/2015 23:27, Shannon Zhao wrote:
> Hi Julien,

Hi Shannon,

Sorry for the late answer I was on holiday. In general it's better to CC 
multiple person and the mailing list as we may not be able to answer in 
short time or not know the answer.

I've CCed the ML and few people which know better than me the status of 
EFI runtime.

> Do you know the status of runtime service for Xen on ARM? Does it
> support runtime service booting with DT? If not, is there a plan to
> support it?

There is no support of runtime EFI on ARM for now and I'm not aware of 
any short plan for this.

> In addition, if you know this, does it support runtime service for Xen
> on x86?

There is some on-going work for EFI runtime on x86. I'm not sure if it 
has been upstream (CCed Daniel for this).

Although, one of there is a fundamental difference between the UEFI boot 
on x86 and ARM. While the code is the same, on ARM the UEFI act as a 
stub and should not be able to communicate via exported variable with 
Xen (we clobber BSS just after the UEFI stub jump on the normal boot start).

I know that the ARM EFI stub is using some shared variable with Xen (I 
have in mind the memory banks see bootinfo). We are very lucky that it's 
working because the variable is living in initdata which somehow is part 
of text (I'm not sure why) and not BSS.
So we should either decide that the stub and xen should be able to 
communicate together or not.

I would be in favor of the former but I don't know what are the view of 
the others.

Regards,

-- 
Julien Grall

       reply	other threads:[~2015-08-26  3:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55D5733B.4050804@huawei.com>
2015-08-26  3:24 ` Julien Grall [this message]
2015-08-26  7:04   ` About runtime service for Xen on ARM Jan Beulich
2015-09-01 13:24     ` Stefano Stabellini
2015-08-26 13:27   ` Shannon Zhao

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=55DD3158.3080003@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=christoffer.dall@linaro.org \
    --cc=daniel.kiper@oracle.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=shannon.zhao@linaro.org \
    --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).