From: Alex Williamson <alex.williamson@redhat.com>
To: Eric Auger <eric.auger@linaro.org>
Cc: bk rakesh <rakeshbkrish@gmail.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
jiang.liu@linux.intel.com
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 [thread overview]
Message-ID: <1426861282.3643.472.camel@redhat.com> (raw)
In-Reply-To: <550C2A66.8040707@linaro.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
prev parent reply other threads:[~2015-03-20 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 7:19 Hardware support for vt-posted interrupts described in vt-directed-io-spec for assigned devices bk rakesh
2015-03-20 9:54 ` bk rakesh
2015-03-20 14:04 ` Alex Williamson
2015-03-20 14:10 ` Eric Auger
2015-03-20 14:21 ` Alex Williamson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1426861282.3643.472.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=eric.auger@linaro.org \
--cc=jiang.liu@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rakeshbkrish@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox