qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/3] VFIO-based PCI device assignment for QEMU 1


From: Cole Robinson
Subject: Re: [Qemu-devel] [PATCH 0/3] VFIO-based PCI device assignment for QEMU 1.2
Date: Tue, 14 Aug 2012 10:53:29 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0

On 08/13/2012 03:31 PM, Anthony Liguori wrote:
> Jan Kiszka <address@hidden> writes:
> 
>> On 2012-08-13 15:58, Avi Kivity wrote:
>>> On 08/13/2012 04:27 PM, Anthony Liguori wrote:
>>>
>>>> Thanks for pushing this forward!  Hopefully this will finally kill off
>>>> qemu-kvm.git for good.
>>>
>>> No, it won't.  vfio requires a 3.6 kernel, which we cannot assume anyone
>>> has.  We'll need the original device assignment code side-by-side.
>>
>> ...which is on my to-do list for 1.3.
> 
> Is there a deprecation plan for the old device assignment code?
> 
> I'm not really against the idea of requiring a new kernel for new
> features.
> 
> From a Fedora/OpenSUSE point of view, would supporting old kernels be a
> requirement to stop shipping qemu-kvm.git over qemu.git?
> 

Speaking as a Fedora maintainer, compatibility with old kernels isn't that
important to us, provided the functionality of the new way is comparable to
the old way.

As far as switching over to qemu.git, I assume there will eventually be a day
when the fork would 'end' and qemu-kvm would stop getting its own releases,
which is when we'd switch. Maybe that assumption is wrong or over simplifying
the trade offs, but if merge work is ongoing I don't see a very compelling
reason to switch.

- Cole



reply via email to

[Prev in Thread] Current Thread [Next in Thread]