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

Re: [Xen-devel] Xen Platform QoS design discussion

>>> On 22.05.14 at 10:19, <dongxiao.xu@xxxxxxxxx> wrote:
>> From: xen-devel-bounces@xxxxxxxxxxxxx 
>> And without seeing the need for any advanced access mechanism,
>> I'm continuing to try to promote D - implement simple, policy free
>> (platform or sysctl) hypercalls providing MSR access to the tool stack
>> (along the lines of the msr.ko Linux kernel driver).
> Do you mean some hypercall implementation like following:
> In this case, Dom0 toolstack actually queries the real physical CPU MSRs.
> struct xen_sysctl_accessmsr      accessmsr
> {
>     unsigned int cpu;
>     unsigned int msr;
>     unsigned long value;
> }
> do_sysctl () {
> ...
> case XEN_SYSCTL_accessmsr:
>     /* store the msr value in accessmsr.value */
>     on_selected_cpus(cpumask_of(cpu), read_msr, &(op->u.accessmsr), 1);
> }

Yes, along those lines, albeit slightly more sophisticated based on
the specific kind of operations needed for e.g. QoS (Andrew had
some comments to the effect that simple read and write operations
alone may not suffice).


Xen-devel mailing list



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