s 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.
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 t
As per PSCI 0.2 spec, if CPU_ON entry_point_address is 64-bit then SMC
call function ID parameter should be set to SMC64 version.
Signed-off-by: Brijesh Singh
---
xen/arch/arm/psci.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/xen/arch/arm/psci.c b/xen
On 10/05/2015 11:03 AM, Julien Grall wrote:
> Hi,
>
> From the commit title, it's not clear that you are touching the PSCI code.
>
> I would rewrite it like:
>
> "xen/arm: psci: use SMC64 function ID when available on ARM64"
>
> On 05/10/15 16:27, Br
As per PSCI 0.2 spec, if CPU_ON entry_point_address is 64-bit then SMC
call function ID parameter should be set to SMC64 version.
Signed-off-by: Brijesh Singh
---
xen/arch/arm/psci.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/xen/arch/arm/psci.c b/xen/arch
On AMD Seattle, Xen failed to boot secondary CPU's. This patch fixes it.
As per PSCI spec, If CPU_ON entry_point_address is 64-bit then function id
parameter should be set to SMC64 version (0xC403).
Signed-off-by: Brijesh Singh
---
xen/arch/arm/psci.c | 4
1 file chang
