From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC PATCH 0/5] QEMU VFIO device assignment Date: Sun, 11 Jul 2010 21:17:21 +0300 Message-ID: <4C3A0AB1.3070302@redhat.com> References: <20100711180910.20121.93313.stgit@localhost6.localdomain6> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, pugs@cisco.com, chrisw@redhat.com, mst@redhat.com To: Alex Williamson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:37667 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753983Ab0GKSRc (ORCPT ); Sun, 11 Jul 2010 14:17:32 -0400 In-Reply-To: <20100711180910.20121.93313.stgit@localhost6.localdomain6> Sender: kvm-owner@vger.kernel.org List-ID: On 07/11/2010 09:09 PM, Alex Williamson wrote: > The following series implements QEMU device assignment using the > proposed VFIO/UIOMMU kernel interfaces. See the last patch for > further vfio description. I've tested this on the v2 VFIO patch, > with a number of fixes hacked in along the way. I'll update when > Tom releases a new version of VFIO. Hopefully this will provide > some support for the usefulness of such an interfaces. Thanks, > > What's the plan for supporting this alongside the existing kvm device assignment code? vfio will only exist in very new kernels, so we have to support the old code for a while to give people chance to adjust (say 12-18 months). Ideally we'd have compatible command line syntax with qemu choosing vfio if available and falling back to kvm device assignment if not. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.