Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753109AbbGIPfJ (ORCPT ); Thu, 9 Jul 2015 11:35:09 -0400 Received: from 8bytes.org ([81.169.241.247]:43723 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751132AbbGIPfA (ORCPT ); Thu, 9 Jul 2015 11:35:00 -0400 Date: Thu, 9 Jul 2015 17:34:58 +0200 From: Joerg Roedel To: Paolo Bonzini Cc: Alex Williamson , 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 Subject: Re: [RFC v2 0/6] IRQ bypass manager and irqfd consumer Message-ID: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <559E8771.9010401@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1246 Lines: 27 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. Joerg -- 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/