From mboxrd@z Thu Jan  1 00:00:00 1970
From: Brijesh Singh <brijeshkumar.singh@amd.com>
Subject: ARM64 EFI runtime
Date: Mon, 12 Oct 2015 13:40:28 -0500
Message-ID: <561BFE9C.2040102@amd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org
Cc: brijeshkumar.singh@amd.com
List-Id: xen-devel@lists.xenproject.org

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