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

Re: [Xen-devel] [PATCH v2 13/13] x86/domctl: Implement XEN_DOMCTL_get_cpu_policy



On Fri, Jul 13, 2018 at 09:03:14PM +0100, Andrew Cooper wrote:
>From: Sergey Dyasli <sergey.dyasli@xxxxxxxxxx>
>
>This finally (after literally years of work!) marks the point where the
>toolstack can ask the hypervisor for the current CPUID configuration of a
>specific domain.
>
>Also extend xen-cpuid's --policy mode to be able to take a domid and dump a
>specific domains CPUID and MSR policy.
>
>Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
>Signed-off-by: Sergey Dyasli <sergey.dyasli@xxxxxxxxxx>
>---
>+
>+/*
>+ * XEN_SYSCTL_{get,set}_cpu_policy (x86 specific)
>+ *
>+ * Query or set the CPUID and MSR policies for a specific domain.

Setting policies isn't introduced in this series. The comments here
should be aligned with what have been implemented.

Thanks
Chao

>+ */
>+struct xen_domctl_cpu_policy {
>+    uint32_t nr_leaves; /* IN/OUT: Number of leaves in/written to
>+                         * 'cpuid_policy'. */
>+    uint32_t nr_msrs;   /* IN/OUT: Number of MSRs in/written to
>+                         * 'msr_domain_policy' */
>+    XEN_GUEST_HANDLE_64(xen_cpuid_leaf_t) cpuid_policy; /* IN/OUT: */
>+    XEN_GUEST_HANDLE_64(xen_msr_entry_t) msr_policy;    /* IN/OUT: */
>+};
>+typedef struct xen_domctl_cpu_policy xen_domctl_cpu_policy_t;
>+DEFINE_XEN_GUEST_HANDLE(xen_domctl_cpu_policy_t);
> #endif
> 

_______________________________________________
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®.