search for: xen_domctl_hypercall_init

...range */ + uint32_t nr_ports; /* size of port range */ + uint8_t allow_access; /* allow or deny access to range? */ +}; +typedef struct xen_domctl_ioport_permission xen_domctl_ioport_permission_t; +DEFINE_XEN_GUEST_HANDLE(xen_domctl_ioport_permission_t); + +#define XEN_DOMCTL_hypercall_init 22 +struct xen_domctl_hypercall_init { + uint64_t gmfn; /* GMFN to be initialised */ +}; +typedef struct xen_domctl_hypercall_init xen_domctl_hypercall_init_t; +DEFINE_XEN_GUEST_HANDLE(xen_domctl_hypercall_init_t); + +#define XEN_DOMCTL_arch_setup 23 +#define _XEN_DOMAINSET...

...+ __PRE_XEN_DOMCTL_READ(settscinfo, tsc_info, info.tsc_mode); + __PRE_XEN_DOMCTL_READ(settscinfo, tsc_info, info.gtsc_khz); + __PRE_XEN_DOMCTL_READ(settscinfo, tsc_info, info.incarnation); + __PRE_XEN_DOMCTL_READ(settscinfo, tsc_info, info.elapsed_nsec); + break; + + case XEN_DOMCTL_hypercall_init: + PRE_XEN_DOMCTL_READ(hypercall_init, gmfn); + break; + + case XEN_DOMCTL_getvcpuinfo: + PRE_XEN_DOMCTL_READ(getvcpuinfo, vcpu); + break; + + case XEN_DOMCTL_scheduler_op: + PRE_XEN_DOMCTL_READ(scheduler_op, sched_id); + PRE_XEN_DOMCTL_READ(scheduler_op, cmd); +...

These two patches were originally part of the XSM series that I have posted, and remain prerequisites for that series. However, they are independent of the XSM changes and are a useful simplification regardless of the use of XSM. The Acked-bys on these patches were provided before rebasing them over the copyback changes in 26268:1b72138bddda, which had minor conflicts that I resolved. [PATCH