[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <549576C7.4030800@redhat.com>
Date: Sat, 20 Dec 2014 14:16:55 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: "Wu, Feng" <feng.wu@...el.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Yang Zhang <yang.z.zhang@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>, Gleb Natapov <gleb@...nel.org>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"joro@...tes.org" <joro@...tes.org>,
Alex Williamson <alex.williamson@...hat.com>,
Jiang Liu <jiang.liu-VuQAYsv1563Yd54FQh9/CA@...lic.gmane.org>
CC: "iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
KVM list <kvm@...r.kernel.org>,
Eric Auger <eric.auger@...aro.org>
Subject: Re: [v3 13/26] KVM: Define a new interface kvm_find_dest_vcpu() for
VT-d PI
On 20/12/2014 00:48, Wu, Feng wrote:
> In my understanding, lowest priority interrupts are always delivered to a
> Single CPU, we need to find the right destination CPU from the cpumask.
Yes, but which CPU however differs every time the interrupt is
delivered. So the emulation here is a bit poor. For now, please limit
PI to fixed interrupts.
> Actually, we don't support posting broadcast/multicast interrupts, because
> the interrupt is associated with one Posted-interrupts descriptor, then one
> vCPU.
Understood.
Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists