Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753553AbbGIQGs (ORCPT ); Thu, 9 Jul 2015 12:06:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33104 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751164AbbGIQGh (ORCPT ); Thu, 9 Jul 2015 12:06:37 -0400 Message-ID: <1436457995.1391.231.camel@redhat.com> Subject: Re: [RFC v2 0/6] IRQ bypass manager and irqfd consumer From: Alex Williamson To: Joerg Roedel Cc: Paolo Bonzini , Eric Auger , eric.auger@st.com, linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, christoffer.dall@linaro.org, marc.zyngier@arm.com, avi.kivity@gmail.com, mtosatti@redhat.com, feng.wu@intel.com, b.reynal@virtualopensystems.com, linux-kernel@vger.kernel.org, patches@linaro.org Date: Thu, 09 Jul 2015 10:06:35 -0600 In-Reply-To: <20150709153458.GX18569@8bytes.org> References: <1436184692-20927-1-git-send-email-eric.auger@linaro.org> <1436289468.1391.89.camel@redhat.com> <20150709122805.GW18569@8bytes.org> <1436451223.1391.219.camel@redhat.com> <559E8771.9010401@redhat.com> <20150709153458.GX18569@8bytes.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1363 Lines: 29 On Thu, 2015-07-09 at 17:34 +0200, Joerg Roedel wrote: > On Thu, Jul 09, 2015 at 04:38:41PM +0200, Paolo Bonzini wrote: > > >> On Tue, Jul 07, 2015 at 11:17:48AM -0600, Alex Williamson wrote: > > > If we think that it's *only* a kvm-vfio interaction then we could add it > > > to virt/kvm/vfio.c. vfio could use symbol_get to avoid a module > > > dependency and effectively disable the code path when not used with kvm. > > > The reverse model of hosting it in vfio and using symbol_get from > > > kvm-vfio would also work. Do we really want to declare it to be > > > kvm-vfio specific though? Another option would be to simply host it > > > under virt/lib with module dependencies for both vfio and kvm. > > > > I wonder if in the future we may have some kind of driver-mediated > > passthrough, e.g. for network drivers. They might use the bypass > > mechanism too. So I think drivers/vfio is too restrictive. > > > > virt/ right now only hosts KVM, but it could for example host lguest > > too. virt/lib/ is okay with me. > > Yeah, virt/lib is probably the best choice. I will make it so. Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/