[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v3 5/6] virt, sched: add cpu pinning to smp_call_sync_on_phys_cpu()
- To: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- From: Juergen Gross <jgross@xxxxxxxx>
- Date: Fri, 1 Apr 2016 11:26:25 +0200
- Cc: x86@xxxxxxxxxx, jeremy@xxxxxxxx, jdelvare@xxxxxxxx, hpa@xxxxxxxxx, akataria@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, rusty@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, chrisw@xxxxxxxxxxxx, mingo@xxxxxxxxxx, david.vrabel@xxxxxxxxxx, Douglas_Warzecha@xxxxxxxx, pali.rohar@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, boris.ostrovsky@xxxxxxxxxx, tglx@xxxxxxxxxxxxx, linux@xxxxxxxxxxxx
- Delivery-date: Fri, 01 Apr 2016 09:26:40 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 01/04/16 11:15, Peter Zijlstra wrote:
> On Fri, Apr 01, 2016 at 11:03:21AM +0200, Juergen Gross wrote:
>>> Maybe just make the vpin thing an option like:
>>>
>>> smp_call_on_cpu(int (*func)(void *), int phys_cpu);
>
>>> Also; is something like the vpin thing possible on KVM? because if we're
>>> going to expose it to generic code like this we had maybe look at wider
>>> support.
>>
>> It is necessary for dom0 under Xen. I don't think there is a need to do
>> this on KVM as a guest has no direct access to e.g. BIOS functions of
>> the real hardware and the host system needs no vcpu pinning. I'm not
>> sure about VMWare.
>
> OK, then can we WARN if .phys=1 and the platform doesn't support it?
>
Yes, good idea.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
