From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: Re: Hardware support for vt-posted interrupts described in vt-directed-io-spec for assigned devices Date: Fri, 20 Mar 2015 08:21:22 -0600 Message-ID: <1426861282.3643.472.camel@redhat.com> References: <1426860291.3643.471.camel@redhat.com> <550C2A66.8040707@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: bk rakesh , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, jiang.liu@linux.intel.com To: Eric Auger Return-path: In-Reply-To: <550C2A66.8040707@linaro.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Fri, 2015-03-20 at 15:10 +0100, Eric Auger wrote: > On 03/20/2015 03:04 PM, Alex Williamson wrote: > > On Fri, 2015-03-20 at 15:24 +0530, bk rakesh wrote: > >> Adding few more information regarding the setup which i had created to > >> test the vt-d posted interrupts for assigned devices, > >> > >> Hardware used for evaluating vt-posted interrupts > >> cpu "E5-2620 v2 @ 2.10GHz" and "S2600CP server board" > >> > >> I had used kernel-3.18 patched with "KVM-VFIO IRQ forward > >> control(posted by eric.auger@linaro.org)", > > > > IRQ forwarding in an ARM technology for handling level triggered > > interrupts, not Intel, not even x86. > > Hi Alex, > > Feng's series relies on few pacth files in "KVM-VFIO IRQ forward > control", basically for KVM_DEV_VFIO_DEVICE group introduction in > KVM-VFIO. This explains why you find some references to that patch here > I guess. Ah yes, makes sense. Thanks, Alex