g;
> > linux-kernel@vger.kernel.org;
> > pbonz...@redhat.com; mtosa...@redhat.com; Joerg Roedel
> > Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
> >
> > [Adding Joerg since he was part of this original idea]
> >
> >
> > There ar
oerg Roedel
> Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
>
> [Adding Joerg since he was part of this original idea]
>
> On Thu, 2015-06-18 at 09:16 +, Wu, Feng wrote:
> >
> >
> > > -Original Message-
> > > From: Alex
ubject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
>
> On Mon, Jun 29, 2015 at 09:14:54AM +, Wu, Feng wrote:
> > Do you mean updating the hardware IRTEs for all the entries in the irq
> > routing table, no matter whether it is the updated one?
>
> Ri
On Mon, Jun 29, 2015 at 09:14:54AM +, Wu, Feng wrote:
> Do you mean updating the hardware IRTEs for all the entries in the irq
> routing table, no matter whether it is the updated one?
Right, that's what I mean. It seems wrong to me to work around the API
interface by creating a diff between
ubject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
>
> Hi Feng,
>
> On Thu, Jun 25, 2015 at 09:11:52AM -0600, Alex Williamson wrote:
> > So the trouble is that QEMU vfio updates a single MSI vector, but that
> > just updates a single entry within a whole table
Hi Feng,
On Thu, Jun 25, 2015 at 09:11:52AM -0600, Alex Williamson wrote:
> So the trouble is that QEMU vfio updates a single MSI vector, but that
> just updates a single entry within a whole table of routes, then the
> whole table is pushed to KVM. But in kvm_set_irq_routing() we have
> access
To: Eric Auger
Cc: Avi Kivity; Wu, Feng; k...@vger.kernel.org;
linux-kernel@vger.kernel.org;
pbonz...@redhat.com; mtosa...@redhat.com
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
On Mon, 2015-06-15 at 18:17 +0200, Eric Auger wrote:
Hi Alex, all,
On 06/12
: kvm-vfio: User API for IRQ forwarding
On Mon, Jun 29, 2015 at 09:14:54AM +, Wu, Feng wrote:
Do you mean updating the hardware IRTEs for all the entries in the irq
routing table, no matter whether it is the updated one?
Right, that's what I mean. It seems wrong to me to work around
On Mon, Jun 29, 2015 at 09:14:54AM +, Wu, Feng wrote:
Do you mean updating the hardware IRTEs for all the entries in the irq
routing table, no matter whether it is the updated one?
Right, that's what I mean. It seems wrong to me to work around the API
interface by creating a diff between
...@redhat.com; mtosa...@redhat.com; Joerg Roedel
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
[Adding Joerg since he was part of this original idea]
There are plenty of details to be filled in, but I think the basics
looks something like the code below. The IRQ bypass
: kvm-vfio: User API for IRQ forwarding
Hi Feng,
On Thu, Jun 25, 2015 at 09:11:52AM -0600, Alex Williamson wrote:
So the trouble is that QEMU vfio updates a single MSI vector, but that
just updates a single entry within a whole table of routes, then the
whole table is pushed to KVM
Hi Feng,
On Thu, Jun 25, 2015 at 09:11:52AM -0600, Alex Williamson wrote:
So the trouble is that QEMU vfio updates a single MSI vector, but that
just updates a single entry within a whole table of routes, then the
whole table is pushed to KVM. But in kvm_set_irq_routing() we have
access to
> > linux-kernel@vger.kernel.org; pbonz...@redhat.com; mtosa...@redhat.com
> > Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
> >
> > On Thu, Jun 18, 2015 at 02:04:08PM -0600, Alex Williamson wrote:
> > > There are plenty of details to be fi
; Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
>
> On Thu, Jun 18, 2015 at 02:04:08PM -0600, Alex Williamson wrote:
> > There are plenty of details to be filled in,
>
> I also need to fill plenty of details in my head first, so here are some
> suggestions
...@redhat.com; mtosa...@redhat.com
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
On Thu, Jun 18, 2015 at 02:04:08PM -0600, Alex Williamson wrote:
There are plenty of details to be filled in,
I also need to fill plenty of details in my head first, so here are some
: kvm-vfio: User API for IRQ forwarding
On Thu, Jun 18, 2015 at 02:04:08PM -0600, Alex Williamson wrote:
There are plenty of details to be filled in,
I also need to fill plenty of details in my head first, so here are some
suggestions based on my current understanding. Please don't hesitate
.com
> Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
>
> On Wed, 2015-06-24 at 18:25 +0200, Eric Auger wrote:
> > Hi Joerg,
> >
> > On 06/24/2015 05:50 PM, Joerg Roedel wrote:
> > > On Mon, Jun 15, 2015 at 06:17:03PM +0200, Eric Auger wrot
; Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
>
> On Thu, Jun 18, 2015 at 02:04:08PM -0600, Alex Williamson wrote:
> > There are plenty of details to be filled in,
>
> I also need to fill plenty of details in my head first, so here are some
> suggestions
On Wed, 2015-06-24 at 18:25 +0200, Eric Auger wrote:
> Hi Joerg,
>
> On 06/24/2015 05:50 PM, Joerg Roedel wrote:
> > On Mon, Jun 15, 2015 at 06:17:03PM +0200, Eric Auger wrote:
> >> I guess this discussion also is relevant wrt "[RFC v6 00/16] KVM-VFIO
> >> IRQ forward control" series? Or is that
Hi Joerg,
On 06/24/2015 05:50 PM, Joerg Roedel wrote:
> On Mon, Jun 15, 2015 at 06:17:03PM +0200, Eric Auger wrote:
>> I guess this discussion also is relevant wrt "[RFC v6 00/16] KVM-VFIO
>> IRQ forward control" series? Or is that "central registry maintained by
>> a posted interrupts manager"
On Mon, Jun 15, 2015 at 06:17:03PM +0200, Eric Auger wrote:
> I guess this discussion also is relevant wrt "[RFC v6 00/16] KVM-VFIO
> IRQ forward control" series? Or is that "central registry maintained by
> a posted interrupts manager" something more specific to x86?
>From what I understood so
On Thu, Jun 18, 2015 at 02:04:08PM -0600, Alex Williamson wrote:
> There are plenty of details to be filled in,
I also need to fill plenty of details in my head first, so here are some
suggestions based on my current understanding. Please don't hesitate to
correct me if where I got something
08/16] KVM: kvm-vfio: User API for IRQ forwarding
On Wed, 2015-06-24 at 18:25 +0200, Eric Auger wrote:
Hi Joerg,
On 06/24/2015 05:50 PM, Joerg Roedel wrote:
On Mon, Jun 15, 2015 at 06:17:03PM +0200, Eric Auger wrote:
I guess this discussion also is relevant wrt [RFC v6 00/16] KVM-VFIO
: kvm-vfio: User API for IRQ forwarding
On Thu, Jun 18, 2015 at 02:04:08PM -0600, Alex Williamson wrote:
There are plenty of details to be filled in,
I also need to fill plenty of details in my head first, so here are some
suggestions based on my current understanding. Please don't hesitate
On Mon, Jun 15, 2015 at 06:17:03PM +0200, Eric Auger wrote:
I guess this discussion also is relevant wrt [RFC v6 00/16] KVM-VFIO
IRQ forward control series? Or is that central registry maintained by
a posted interrupts manager something more specific to x86?
From what I understood so far, the
On Thu, Jun 18, 2015 at 02:04:08PM -0600, Alex Williamson wrote:
There are plenty of details to be filled in,
I also need to fill plenty of details in my head first, so here are some
suggestions based on my current understanding. Please don't hesitate to
correct me if where I got something
Hi Joerg,
On 06/24/2015 05:50 PM, Joerg Roedel wrote:
On Mon, Jun 15, 2015 at 06:17:03PM +0200, Eric Auger wrote:
I guess this discussion also is relevant wrt [RFC v6 00/16] KVM-VFIO
IRQ forward control series? Or is that central registry maintained by
a posted interrupts manager something
On Wed, 2015-06-24 at 18:25 +0200, Eric Auger wrote:
Hi Joerg,
On 06/24/2015 05:50 PM, Joerg Roedel wrote:
On Mon, Jun 15, 2015 at 06:17:03PM +0200, Eric Auger wrote:
I guess this discussion also is relevant wrt [RFC v6 00/16] KVM-VFIO
IRQ forward control series? Or is that central
gt; > Cc: Avi Kivity; Wu, Feng; k...@vger.kernel.org;
> > linux-kernel@vger.kernel.org;
> > pbonz...@redhat.com; mtosa...@redhat.com
> > Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
> >
> > On Mon, 2015-06-15 at 18:17 +0200, Eric Auger wrote:
June 12, 2015 3:59 AM
> > >>>>> To: Wu, Feng; k...@vger.kernel.org; linux-kernel@vger.kernel.org
> > >>>>> Cc: pbonz...@redhat.com; mtosa...@redhat.com;
> > >>>>> alex.william...@redhat.com; eric.au...@linaro.org
> > >>>
...@vger.kernel.org;
linux-kernel@vger.kernel.org;
pbonz...@redhat.com; mtosa...@redhat.com
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
On Mon, 2015-06-15 at 18:17 +0200, Eric Auger wrote:
Hi Alex, all,
On 06/12/2015 09:03 PM, Alex Williamson wrote:
On Fri, 2015-06
...@linaro.org
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
On 06/11/2015 01:51 PM, Feng Wu wrote:
From: Eric Auger eric.au...@linaro.org
This patch adds and documents a new KVM_DEV_VFIO_DEVICE
group
and 2 device attributes: KVM_DEV_VFIO_DEVICE_FORWARD_IRQ
nel.org
> >>>>> Cc: pbonz...@redhat.com; mtosa...@redhat.com;
> >>>>> alex.william...@redhat.com; eric.au...@linaro.org
> >>>>> Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
> >>>>>
> >
gt;>>> From: Avi Kivity [mailto:avi.kiv...@gmail.com]
>>>>> Sent: Friday, June 12, 2015 3:59 AM
>>>>> To: Wu, Feng; k...@vger.kernel.org; linux-kernel@vger.kernel.org
>>>>> Cc: pbonz...@redhat.com; mtosa...@redhat.com;
>>>>> ale
.org
> Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
>
> On Fri, 2015-06-12 at 21:48 +0300, Avi Kivity wrote:
> > On 06/12/2015 06:41 PM, Alex Williamson wrote:
> > > On Fri, 2015-06-12 at 00:23 +, Wu, Feng wrote:
> > >>> -Origi
, June 12, 2015 3:59 AM
To: Wu, Feng; k...@vger.kernel.org; linux-kernel@vger.kernel.org
Cc: pbonz...@redhat.com; mtosa...@redhat.com;
alex.william...@redhat.com; eric.au...@linaro.org
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
On 06/11/2015 01:51 PM, Feng
: Friday, June 12, 2015 3:59 AM
To: Wu, Feng; k...@vger.kernel.org; linux-kernel@vger.kernel.org
Cc: pbonz...@redhat.com; mtosa...@redhat.com;
alex.william...@redhat.com; eric.au...@linaro.org
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
On 06/11/2015 01:51 PM, Feng Wu
-
From: Avi Kivity [mailto:avi.kiv...@gmail.com]
Sent: Friday, June 12, 2015 3:59 AM
To: Wu, Feng; k...@vger.kernel.org; linux-kernel@vger.kernel.org
Cc: pbonz...@redhat.com; mtosa...@redhat.com;
alex.william...@redhat.com; eric.au...@linaro.org
Subject: Re: [v4 08/16] KVM: kvm-vfio
t: Friday, June 12, 2015 3:59 AM
> >>> To: Wu, Feng; k...@vger.kernel.org; linux-kernel@vger.kernel.org
> >>> Cc: pbonz...@redhat.com; mtosa...@redhat.com;
> >>> alex.william...@redhat.com; eric.au...@linaro.org
> >>> Subject: Re: [v4 08/16]
...@redhat.com; mtosa...@redhat.com;
alex.william...@redhat.com; eric.au...@linaro.org
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
On 06/11/2015 01:51 PM, Feng Wu wrote:
From: Eric Auger
This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
and 2 device attributes
.@redhat.com; mtosa...@redhat.com;
> > alex.william...@redhat.com; eric.au...@linaro.org
> > Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
> >
> > On 06/11/2015 01:51 PM, Feng Wu wrote:
> > > From: Eric Auger
> > >
> > > This pa
...@redhat.com; mtosa...@redhat.com;
alex.william...@redhat.com; eric.au...@linaro.org
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
On 06/11/2015 01:51 PM, Feng Wu wrote:
From: Eric Auger eric.au...@linaro.org
This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
and 2 device
...@vger.kernel.org; linux-kernel@vger.kernel.org
Cc: pbonz...@redhat.com; mtosa...@redhat.com;
alex.william...@redhat.com; eric.au...@linaro.org
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
On 06/11/2015 01:51 PM, Feng Wu wrote:
From: Eric Auger eric.au...@linaro.org
...@redhat.com; eric.au...@linaro.org
Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
On 06/11/2015 01:51 PM, Feng Wu wrote:
From: Eric Auger eric.au...@linaro.org
This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
and 2 device attributes
.org
> Subject: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
>
> On 06/11/2015 01:51 PM, Feng Wu wrote:
> > From: Eric Auger
> >
> > This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
> > and 2 device attributes: KVM_DEV_VFIO_DEVICE
t: Re: [v4 08/16] KVM: kvm-vfio: User API for IRQ forwarding
>
> Hi Feng,
> On 06/11/2015 12:51 PM, Feng Wu wrote:
> > From: Eric Auger
> >
> > This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
> > and 2 device attributes: KVM_DEV_VFIO_DEVICE_FORWARD_I
On 06/11/2015 01:51 PM, Feng Wu wrote:
From: Eric Auger
This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
and 2 device attributes: KVM_DEV_VFIO_DEVICE_FORWARD_IRQ,
KVM_DEV_VFIO_DEVICE_UNFORWARD_IRQ. The purpose is to be able
to set a VFIO device IRQ as forwarded or not forwarded.
Hi Feng,
On 06/11/2015 12:51 PM, Feng Wu wrote:
> From: Eric Auger
>
> This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
> and 2 device attributes: KVM_DEV_VFIO_DEVICE_FORWARD_IRQ,
> KVM_DEV_VFIO_DEVICE_UNFORWARD_IRQ. The purpose is to be able
> to set a VFIO device IRQ as forwarded
From: Eric Auger
This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
and 2 device attributes: KVM_DEV_VFIO_DEVICE_FORWARD_IRQ,
KVM_DEV_VFIO_DEVICE_UNFORWARD_IRQ. The purpose is to be able
to set a VFIO device IRQ as forwarded or not forwarded.
the command takes as argument a handle to
From: Eric Auger eric.au...@linaro.org
This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
and 2 device attributes: KVM_DEV_VFIO_DEVICE_FORWARD_IRQ,
KVM_DEV_VFIO_DEVICE_UNFORWARD_IRQ. The purpose is to be able
to set a VFIO device IRQ as forwarded or not forwarded.
the command takes as
Hi Feng,
On 06/11/2015 12:51 PM, Feng Wu wrote:
From: Eric Auger eric.au...@linaro.org
This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
and 2 device attributes: KVM_DEV_VFIO_DEVICE_FORWARD_IRQ,
KVM_DEV_VFIO_DEVICE_UNFORWARD_IRQ. The purpose is to be able
to set a VFIO device
08/16] KVM: kvm-vfio: User API for IRQ forwarding
On 06/11/2015 01:51 PM, Feng Wu wrote:
From: Eric Auger eric.au...@linaro.org
This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
and 2 device attributes: KVM_DEV_VFIO_DEVICE_FORWARD_IRQ,
KVM_DEV_VFIO_DEVICE_UNFORWARD_IRQ
-Original Message-
From: Eric Auger [mailto:eric.au...@linaro.org]
Sent: Thursday, June 11, 2015 9:38 PM
To: Wu, Feng; k...@vger.kernel.org; linux-kernel@vger.kernel.org
Cc: pbonz...@redhat.com; mtosa...@redhat.com;
alex.william...@redhat.com
Subject: Re: [v4 08/16] KVM: kvm-vfio
On 06/11/2015 01:51 PM, Feng Wu wrote:
From: Eric Auger eric.au...@linaro.org
This patch adds and documents a new KVM_DEV_VFIO_DEVICE group
and 2 device attributes: KVM_DEV_VFIO_DEVICE_FORWARD_IRQ,
KVM_DEV_VFIO_DEVICE_UNFORWARD_IRQ. The purpose is to be able
to set a VFIO device IRQ as
54 matches
Mail list logo
