Hello, I've noticed that the SILO code causes the following debug spew:
(XEN) XSM Framework v1.0.0 initialized (XEN) Initialising XSM SILO mode (XEN) dummy.c:31: Had to override the security_domaininfo security operation with the dummy one. (XEN) dummy.c:32: Had to override the domain_create security operation with the dummy one. ... (XEN) dummy.c:158: Had to override the xen_version security operation with the dummy one. (XEN) dummy.c:159: Had to override the domain_resource_map security operation with the dummy one. (XEN) microcode: CPU0 updated from revision 0x1a to 0x25, date = 2018-04-02 (XEN) xstate: size: 0x340 and states: 0x7 which is a side effect of silo_xsm_ops only implementing a few of the hooks, falling back to dummy for the rest. Presumably we don't want to special case SILO when overriding the hooks. Would having silo_init() explicitly copy from dummy be ok? ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
