[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v7 4/6] xen/arm: zynqmp: implement zynqmp_eemi



Hi,

On 12/17/18 10:10 PM, Stefano Stabellini wrote:
+    /* These calls are safe and always allowed.  */
+    case EEMI_FID(ZYNQMP_SIP_SVC_CALL_COUNT):
+    case EEMI_FID(ZYNQMP_SIP_SVC_UID):
+    case EEMI_FID(ZYNQMP_SIP_SVC_VERSION):
+    case EEMI_FID(PM_GET_TRUSTZONE_VERSION):
+    case EEMI_FID(PM_GET_API_VERSION):

Above you say the call to PM_GET_API_VERSION are safe and always allowed. But looking at the ATF implementation the first call to PM_GET_API_VERSION will enable IPI IRQ.

AFAICT, Dom0 will be the only domain to access IPI. So what happen if, in the Dom0less case, the guest is booting before and calling PM_GET_API_VERSION?

I haven't looked in depth the other SIP functions to see whether there are other potential issue.

Cheers,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.