From: Brijesh Singh <brijeshkumar.singh@amd.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: brijeshkumar.singh@amd.com, xen-devel@lists.xen.org
Subject: Re: ARM64 EFI runtime
Date: Tue, 13 Oct 2015 09:31:29 -0500 [thread overview]
Message-ID: <561D15C1.1080203@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510131056171.1179@kaball.uk.xensource.com>
Thanks for update Stefano,
If you have some sample code on private git then please point me at it. I should be able to help on both development and testing on Seattle platform.
-Brijesh
On 10/13/2015 04:57 AM, Stefano Stabellini wrote:
> Hi Brijesh,
>
> EFI runtime services are not currently exported to Dom0. They are still
> a work in progress.
>
> Regards,
>
> Stefano
>
> On Mon, 12 Oct 2015, Brijesh Singh wrote:
>> Hi All,
>>
>> I noticed that DOM0 kernel fails to get time via RTC device on AMD ARM64 (Seattle) platform. On this platform Linux uses rtc-efi driver to get the time through EFI runtime services, and I know for sure that driver works well outside the Xen environment. It seems that devicetree passed to DOM0 through Xen does not contain UEFI system table information hence DOM0 fails to probe rtc-efi platform driver. I see the below message in DOM0 dmesg log
>>
>> [ 0.000000] bootconsole [uart0] enabled
>> [ 0.000000] efi: Getting EFI parameters from FDT:
>> [ 0.000000] efi: UEFI not found.
>> [ 0.000000] cma: Reserved 16 MiB at 0x00000083df000000
>>
>>
>> Looking at Xen's common/efi/runtime.c indicates that EFI runtime services are not yet supported on ARM platform, is anyone working on it?
>>
>> Thanks
>> Brijesh
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
next prev parent reply other threads:[~2015-10-13 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 18:40 ARM64 EFI runtime Brijesh Singh
2015-10-13 9:57 ` Stefano Stabellini
2015-10-13 14:31 ` Brijesh Singh [this message]
2015-10-13 14:55 ` Stefano Stabellini
2015-10-13 16:20 ` Julien Grall
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=561D15C1.1080203@amd.com \
--to=brijeshkumar.singh@amd.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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.