* ARM64 EFI runtime @ 2015-10-12 18:40 Brijesh Singh 2015-10-13 9:57 ` Stefano Stabellini 0 siblings, 1 reply; 5+ messages in thread From: Brijesh Singh @ 2015-10-12 18:40 UTC (permalink / raw) To: xen-devel; +Cc: brijeshkumar.singh 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ARM64 EFI runtime 2015-10-12 18:40 ARM64 EFI runtime Brijesh Singh @ 2015-10-13 9:57 ` Stefano Stabellini 2015-10-13 14:31 ` Brijesh Singh 0 siblings, 1 reply; 5+ messages in thread From: Stefano Stabellini @ 2015-10-13 9:57 UTC (permalink / raw) To: Brijesh Singh; +Cc: xen-devel 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 > ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ARM64 EFI runtime 2015-10-13 9:57 ` Stefano Stabellini @ 2015-10-13 14:31 ` Brijesh Singh 2015-10-13 14:55 ` Stefano Stabellini 0 siblings, 1 reply; 5+ messages in thread From: Brijesh Singh @ 2015-10-13 14:31 UTC (permalink / raw) To: Stefano Stabellini; +Cc: brijeshkumar.singh, xen-devel 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 >> ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ARM64 EFI runtime 2015-10-13 14:31 ` Brijesh Singh @ 2015-10-13 14:55 ` Stefano Stabellini 2015-10-13 16:20 ` Julien Grall 0 siblings, 1 reply; 5+ messages in thread From: Stefano Stabellini @ 2015-10-13 14:55 UTC (permalink / raw) To: Brijesh Singh; +Cc: xen-devel, Stefano Stabellini Hi Brijesh, passing EFI tables to dom0 is still under work by Shannon, see: http://marc.info/?l=xen-devel&m=144321258920213. For now you could simply reuse the existing linux uefi device tree nodes, see Documentation/arm/uefi.txt and the existing acpi patch series for Xen, which also introduces passing efi tables to dom0: http://marc.info/?l=xen-devel&m=143189314630953. Once dom0 knows about efi, then it is just a matter of enabling the existing PV runtime services on arm64, see drivers/xen/efi.c. On Tue, 13 Oct 2015, Brijesh Singh wrote: > 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 > >> > ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ARM64 EFI runtime 2015-10-13 14:55 ` Stefano Stabellini @ 2015-10-13 16:20 ` Julien Grall 0 siblings, 0 replies; 5+ messages in thread From: Julien Grall @ 2015-10-13 16:20 UTC (permalink / raw) To: Stefano Stabellini, Brijesh Singh; +Cc: xen-devel On 13/10/15 15:55, Stefano Stabellini wrote: > Hi Brijesh, > > passing EFI tables to dom0 is still under work by Shannon, see: > http://marc.info/?l=xen-devel&m=144321258920213. For now you could > simply reuse the existing linux uefi device tree nodes, see > Documentation/arm/uefi.txt and the existing acpi patch series for Xen, > which also introduces passing efi tables to dom0: > http://marc.info/?l=xen-devel&m=143189314630953. > > Once dom0 knows about efi, then it is just a matter of enabling the > existing PV runtime services on arm64, see drivers/xen/efi.c. That's not true. There is work to do in Xen in order to support efi runtime. The hypercall to call runtime services (XENPF_efi_runtime_call) is not plumbed and most of the code in common/efi/runtime.c is not built. Regards, -- Julien Grall ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-10-13 16:20 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2015-10-12 18:40 ARM64 EFI runtime Brijesh Singh 2015-10-13 9:57 ` Stefano Stabellini 2015-10-13 14:31 ` Brijesh Singh 2015-10-13 14:55 ` Stefano Stabellini 2015-10-13 16:20 ` Julien Grall
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.