[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151008074153.GB19331@redhat.com>
Date: Thu, 8 Oct 2015 10:41:53 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Gleb Natapov <gleb@...lladb.com>
Cc: Avi Kivity <avi@...lladb.com>,
Alex Williamson <alex.williamson@...hat.com>,
Vlad Zolotarov <vladz@...udius-systems.com>,
Greg KH <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, hjk@...sjkoch.de, corbet@....net,
bruce.richardson@...el.com, avi@...udius-systems.com,
gleb@...udius-systems.com, stephen@...workplumber.org,
alexander.duyck@...il.com
Subject: Re: [PATCH v3 2/3] uio_pci_generic: add MSI/MSI-X support
On Thu, Oct 08, 2015 at 07:19:13AM +0300, Gleb Natapov wrote:
> Well
> the alternative is to add /dev/vfio/nommu like you've said, but what
> would be the difference between this and uio eludes me.
Are you familiar with vfio that you ask such a question?
Here's the vfio pci code:
$ wc -l drivers/vfio/pci/*
27 drivers/vfio/pci/Kconfig
4 drivers/vfio/pci/Makefile
1217 drivers/vfio/pci/vfio_pci.c
1602 drivers/vfio/pci/vfio_pci_config.c
675 drivers/vfio/pci/vfio_pci_intrs.c
92 drivers/vfio/pci/vfio_pci_private.h
238 drivers/vfio/pci/vfio_pci_rdwr.c
3855 total
There's some code dealing with iommu groups in
drivers/vfio/pci/vfio_pci.c,
but most of it is validating input and
presenting a consistent interface to userspace.
This is exactly what's missing here.
There's also drivers/vfio/virqfd.c which deals
with sending interrupts over eventfds correctly.
--
MST
--
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