[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] IRQ affinity: Xen view different from pvops (konrad-pcifront) domU
>>> On 10.11.10 at 21:18, Dante Cinco <dantecinco@xxxxxxxxx> wrote: > After seeing your response (cs 21625, x86: IRQ affinity should track > vCPU affinity), I installed the latest xen-unstable-4.1 (cs 22382) and > the result is the same --- IRQ affinity in Xen is set to all F's after > explicitly setting the IRQ smp_affinity in domU to a specific CPU. I > do have the VCPUs assigned to domU pinned to PCPUs on a one-to-one > basis (VCPU0 -> PCPU0, VCPU1 -> PCPU1, etc.). You may need to do some debugging then to find out what's not working in your case. > My system has 24 PCPUs (dual socket X5650 Xeon/6-core Westmere) but > I'm only assigning the first 16 CPUs to domU and the VCPUs are pinned > to their respective PCPU. The part I don't understand is if the IRQ > affinity per Xen (all F's) is correct, how does the interrupt get > handled if it is directed to a PCPU that is not assigned/pinned to a > VCPU in domU? Since the guest handles event channel signals only, all it takes is binding the event channel to the correct vCPU. When the channel gets signaled, that vCPU will call the handler. Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |