From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brijesh Singh Subject: Re: ARM64 EFI runtime Date: Tue, 13 Oct 2015 09:31:29 -0500 Message-ID: <561D15C1.1080203@amd.com> References: <561BFE9C.2040102@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: brijeshkumar.singh@amd.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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 >>