From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH 0/3] VFIO-based PCI device assignment for QEMU 1.2 Date: Mon, 13 Aug 2012 14:31:13 -0500 Message-ID: <87393qmvwe.fsf@codemonkey.ws> References: <20120801050241.22163.78549.stgit@bling.home> <87pq6uvs52.fsf@codemonkey.ws> <502907EA.9030606@redhat.com> <5029097B.8050706@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Alex Williamson , "qemu-devel\@nongnu.org" , "kvm\@vger.kernel.org" , "aik\@ozlabs.ru" , Benjamin Herrenschmidt , Cole Robinson , Alex Graf To: Jan Kiszka , Avi Kivity Return-path: Received: from e7.ny.us.ibm.com ([32.97.182.137]:35175 "EHLO e7.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752099Ab2HMTck (ORCPT ); Mon, 13 Aug 2012 15:32:40 -0400 Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 13 Aug 2012 15:32:39 -0400 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 707D26E80BE for ; Mon, 13 Aug 2012 15:31:30 -0400 (EDT) Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q7DJVOKW131068 for ; Mon, 13 Aug 2012 15:31:26 -0400 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q7DJVN1J026264 for ; Mon, 13 Aug 2012 13:31:24 -0600 In-Reply-To: <5029097B.8050706@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: Jan Kiszka 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? Since distros ship new kernels and new userspaces, I don't think distros would care so I'm not sure who we're trying to support old kernels for. Regards, Anthony Liguori > > Jan > > -- > Siemens AG, Corporate Technology, CT RTC ITP SDP-DE > Corporate Competence Center Embedded Linux > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html