[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150709122805.GW18569@8bytes.org>
Date: Thu, 9 Jul 2015 14:28:05 +0200
From: Joerg Roedel <joro@...tes.org>
To: Alex Williamson <alex.williamson@...hat.com>
Cc: Eric Auger <eric.auger@...aro.org>, eric.auger@...com,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu,
kvm@...r.kernel.org, christoffer.dall@...aro.org,
marc.zyngier@....com, pbonzini@...hat.com, avi.kivity@...il.com,
mtosatti@...hat.com, feng.wu@...el.com,
b.reynal@...tualopensystems.com, linux-kernel@...r.kernel.org,
patches@...aro.org
Subject: Re: [RFC v2 0/6] IRQ bypass manager and irqfd consumer
On Tue, Jul 07, 2015 at 11:17:48AM -0600, Alex Williamson wrote:
> Hosting the bypass manager in kernel/irq seemed appropriate, but really
> it could be anywhere. Does anyone have a different preference or
> specifically want it under their scope? We had originally thought of
> this as an IOMMU service, but I think we've generalized it beyond that.
> I expect we should also add the necessary hooks to turn it into a
> loadable module to keep the tinification folks happy, I'll incorporate
> the current working changes and post a version with that.
Yeah, this is only an IOMMU service on x86, afaik. So drivers/iommu is
probably the wrong place to host it.
Will there be any other producers than VFIO or any other consumers than
KVM? If not, it should live in one of these spaces. KVM is probably the
best choice, as any hardware feature that uses this targets
virtualization, so there will hardly ever be another consumer than KVM.
Joerg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists