[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
- To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxx>
- From: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
- Date: Fri, 17 Aug 2018 17:22:39 -0400
- Cc: Sergey Dyasli <sergey.dyasli@xxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Delivery-date: Fri, 17 Aug 2018 21:22:54 +0000
- Ironport-phdr: 9a23:9h6KQRxx3KyTdwvXCy+O+j09IxM/srCxBDY+r6Qd0ugVK/ad9pjvdHbS+e9qxAeQG9mDtbQc06L/iOPJYSQ4+5GPsXQPItRndiQuroEopTEmG9OPEkbhLfTnPGQQFcVGU0J5rTngaRAGUMnxaEfPrXKs8DUcBgvwNRZvJuTyB4Xek9m72/q99pHPYghEniaxba9vJxiqsAvdsdUbj5F/Iagr0BvJpXVIe+VSxWx2IF+Yggjx6MSt8pN96ipco/0u+dJOXqX8ZKQ4UKdXDC86PGAv5c3krgfMQA2S7XYBSGoWkx5IAw/Y7BHmW5r6ryX3uvZh1CScIMb7Vq4/Vyi84Kh3SR/okCYHOCA/8GHLkcx7kaZXrAu8qxBj34LYZYeYO/RkfqPZYNgUW2xPUMhMXCBFG4+wcZcDA+8HMO1FrYfyukEOoAOjCweyCuPhyjxGiHH40qI10esuDQ7I0Rc8H98MqnnYsMn5OakQXO2z0aLGzS/Db/RT2Trl5obHaBYhofCSUrJ0bMHfx1cgHB7EgFWKs4PqJT2V3fkKvmeG4OpvSPygi2E9qw5ruTWv2scthZXJhoIS0FzE8z55z5wvKd23T057f8epHZ1NvC+ZL4t7Wt4uTm5ntSogyrAKpIS3cDYFxZg53RLTdvqKeJWS7B35TuaeOzJ4iWpgeLK4mhm971Ctyvb5VsmoyFZKqTdFksXUunANyRPT7s+HR+Nh/ki7wzaP1h3T6vpeLUA1k6rbJZkhwqUumZUPq0jDAi/3l1n2jK+RbEkk/PSn6//7bbn8o5+cNot0hhn/MqQohMO/Hfw1PhUBUmWU4+ix1KDv8VfnTLhFkPE6iLTVvIjfJcsBp665BwFV0pwk6xa6FzqpzdsYkmQZI1JKYhKIlZPkO03OIf/kDfe/hE6gkDFwx//cJLHhDZLNLmbbnLf7Ybl981JcyBY0zd1H/Z1UDKwOIOjtVU7/rtDXEhg5Mwusw+n5EtVw2JgTVn6OAq+FKqPSsFCJ6vgzLOmLYY8foCz9JOQ95/7ykX85nkcQfKa30psRcXy3A+ppI1uHbnromdoBFWYKvhEiTOzxklGDXiBcZ3CoU6I7/DE7B5qsDZ3fSYC1nLyBwCC7E4VNZm9YEFCMHmnndoWeV/gRaCOdONRhkjgFVbW6V4Ah1A2utBX7y7toNObb5ioYtZf73thv++LTjQ0y9SBzD8mF12+AUn97nn4MRz83wK9/oVdwykye0ahjnfNUD8Bc5/RMUg0iL57T0/R6C8zuWgLGZtqHS0ypQtO8DT81VN0+39wOY116G9WklR3MwTeqD6UJmLyKGJw06KPc3nfrK8lhzHbG0bErj0M6TctXKW2mmql/+hDdBoHXkkWVjaKqdaUB3CLT72qM0WuOvF1CUA5xXqTJR2wQZkzTrd7h/EPNU6euCag7MgtG0cOCMKxKatL3glVcXvvjIM7RY3+qlmisBBaI2qmMbIvlemkHwCrdD00EwEgv+iOvMwQkCzjpiGXZFDF0XQbmZU/2/PY4o3S8VkIulCmBblF71qrz8RkQ07jUe/4Vm74Jpiol42FkEVD409/IBt6oowt6YL4acd47plBd2jSKmRZ6O8mMJqZji1pWXwk/kFnn3hs/XolPncUltnoC0Bt5KaXe1khIMTyfw8ajafXsNmDu8UX3OObt0VbE3YPTo/1X5Q==
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 07/13/2018 04:03 PM, 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>
Since this is a read operation, it should have a new access vector (probably
get_cpuid) instead of sitting under set_cpuid so that it is possible to allow
viewing the policy without allowing it to be changed (useful for migration out,
introspection, or duplicating the settings on a now-protected domain).
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
