Wu, Feng wrote on 2014-11-13:
>
>
> Zhang, Yang Z wrote on 2014-11-13:
>> k...@vger.kernel.org; io...@lists.linux-foundation.org;
>> linux-kernel@vger.kernel.org
>> Subject: RE: [PATCH 05/13] KVM: Update IRTE according to guest
>> interrupt configuration changes
..@kernel.org;
> k...@vger.kernel.org; io...@lists.linux-foundation.org;
> linux-kernel@vger.kernel.org
> Subject: RE: [PATCH 05/13] KVM: Update IRTE according to guest interrupt
> configuration changes
>
> Wu, Feng wrote on 2014-11-13:
> >
> >
> > kvm-ow...@vger.kernel.
Wu, Feng wrote on 2014-11-13:
>
>
> kvm-ow...@vger.kernel.org wrote on 2014-11-12:
>> k...@vger.kernel.org; io...@lists.linux-foundation.org;
>> linux-kernel@vger.kernel.org
>> Subject: Re: [PATCH 05/13] KVM: Update IRTE according to guest
>> interrupt config
On Wed, 2014-11-12 at 10:14 +0100, Paolo Bonzini wrote:
>
> On 12/11/2014 04:42, Zhang, Yang Z wrote:
> > Personally, I think this feature will be helpful to the legacy device
> > assignment. Agree, vfio is the right solution for future feature
> > enabling. But the old kvm without the good vfio s
On 12/11/2014 10:19, Wu, Feng wrote:
>> You can certainly backport these patches to distros that do not have
>> VFIO. But upstream we should work on VFIO first. VFIO has feature
>> parity with legacy device assignment, and adding a new feature that is
>> not in VFIO would be a bad idea.
>>
>> B
h...@zytor.com; x...@kernel.org;
> k...@vger.kernel.org; io...@lists.linux-foundation.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 05/13] KVM: Update IRTE according to guest interrupt
> configuration changes
>
>
>
> On 12/11/2014 04:42, Zhang, Yang Z wrote:
&g
On 12/11/2014 04:42, Zhang, Yang Z wrote:
> Personally, I think this feature will be helpful to the legacy device
> assignment. Agree, vfio is the right solution for future feature
> enabling. But the old kvm without the good vfio supporting is still
> used largely today. The user really looking
Paolo Bonzini wrote on 2014-11-11:
>
>
> On 11/11/2014 10:20, Wu, Feng wrote:
>>> Since legacy KVM device assignment is effectively deprecated, have
>>> you considered how we might do this with VFIO? Thanks,
>>
>> I haven't thought about how to enable this in VFIO so far. I think I
>> can conti
..@kernel.org;
> k...@vger.kernel.org; io...@lists.linux-foundation.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 05/13] KVM: Update IRTE according to guest interrupt
> configuration changes
>
>
>
> On 11/11/2014 10:20, Wu, Feng wrote:
> > > Since leg
..@kernel.org;
> k...@vger.kernel.org; io...@lists.linux-foundation.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 05/13] KVM: Update IRTE according to guest interrupt
> configuration changes
>
>
>
> On 11/11/2014 10:20, Wu, Feng wrote:
> > > Since leg
On 11/11/2014 10:20, Wu, Feng wrote:
> > Since legacy KVM device assignment is effectively deprecated, have you
> > considered how we might do this with VFIO? Thanks,
>
> I haven't thought about how to enable this in VFIO so far. I think I can
> continue to
> implement that if needed after thi
...@zytor.com;
> x...@kernel.org; k...@vger.kernel.org; io...@lists.linux-foundation.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 05/13] KVM: Update IRTE according to guest interrupt
> configuration changes
>
> On Mon, 2014-11-10 at 14:26 +0800, Feng Wu wrote:
> > When
...@zytor.com;
> x...@kernel.org; k...@vger.kernel.org; io...@lists.linux-foundation.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 05/13] KVM: Update IRTE according to guest interrupt
> configuration changes
>
> On Mon, 2014-11-10 at 14:26 +0800, Feng Wu wrote:
> > When
On Mon, 2014-11-10 at 14:26 +0800, Feng Wu wrote:
> When guest changes its interrupt configuration (such as, vector, etc.)
> for direct-assigned devices, we need to update the associated IRTE
> with the new guest vector, so external interrupts from the assigned
> devices can be injected to guests w
When guest changes its interrupt configuration (such as, vector, etc.)
for direct-assigned devices, we need to update the associated IRTE
with the new guest vector, so external interrupts from the assigned
devices can be injected to guests without VM-Exit.
The current method of handling guest lowe
15 matches
Mail list logo
