> -----Original Message----- > From: Don Dutile [mailto:ddutile@xxxxxxxxxx] > Sent: Monday, October 28, 2013 8:30 PM > To: Bhushan Bharat-R65777 > Cc: Antonios Motakis; kvmarm@xxxxxxxxxxxxxxxxxxxxx; > alex.williamson@xxxxxxxxxx; linux-samsung-soc@xxxxxxxxxxxxxxx; > kvm@xxxxxxxxxxxxxxx; agraf@xxxxxxx; Yoder Stuart-B08248; > iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx; tech@xxxxxxxxxxxxxxxxxxxxxx > Subject: Re: [PATCH 2/7] Initial skeleton of VFIO support for Device Tree > based devices > > On 09/30/2013 11:37 AM, Bhushan Bharat-R65777 wrote: > > > > > >> -----Original Message----- > >> From: iommu-bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx [mailto:iommu- > >> bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Antonios Motakis > >> Sent: Monday, September 30, 2013 8:59 PM > >> To: kvmarm@xxxxxxxxxxxxxxxxxxxxx; alex.williamson@xxxxxxxxxx > >> Cc: linux-samsung-soc@xxxxxxxxxxxxxxx; kvm@xxxxxxxxxxxxxxx; > agraf@xxxxxxx; Yoder > >> Stuart-B08248; iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx; Antonios Motakis; > >> tech@xxxxxxxxxxxxxxxxxxxxxx > >> Subject: [PATCH 2/7] Initial skeleton of VFIO support for Device Tree > based > >> devices > >> > >> Platform devices in the Linux kernel are usually managed by the DT > interface. > >> This patch forms the base to support these kind of devices with VFIO. > >> > >> Signed-off-by: Antonios Motakis<a.motakis@xxxxxxxxxxxxxxxxxxxxxx> > >> --- > >> drivers/vfio/Kconfig | 11 +++ > >> drivers/vfio/Makefile | 1 + > >> drivers/vfio/vfio_platform.c | 187 > +++++++++++++++++++++++++++++++++++++++++++ > >> include/uapi/linux/vfio.h | 1 + > >> 4 files changed, 200 insertions(+) > >> create mode 100644 drivers/vfio/vfio_platform.c > >> > >> diff --git a/drivers/vfio/Kconfig b/drivers/vfio/Kconfig index > 1f84eda..35254b7 > >> 100644 > >> --- a/drivers/vfio/Kconfig > >> +++ b/drivers/vfio/Kconfig > >> @@ -13,4 +13,15 @@ menuconfig VFIO > >> > >> If you don't know what to do here, say N. > >> > >> +config VFIO_PLATFORM > >> + tristate "VFIO support for device tree based platform devices" > >> + depends on VFIO&& EVENTFD&& OF > >> + help > >> + Support for platform devices with VFIO. This is required to make > >> + use of platform devices present on device tree nodes using the > VFIO > >> + framework. Devices that are not described in the device tree > cannot > >> + be used by this driver. > >> + > >> + If you don't know what to do here, say N. > >> + > >> source "drivers/vfio/pci/Kconfig" > >> diff --git a/drivers/vfio/Makefile b/drivers/vfio/Makefile index > >> 2398d4a..575c8dd 100644 > >> --- a/drivers/vfio/Makefile > >> +++ b/drivers/vfio/Makefile > >> @@ -1,3 +1,4 @@ > >> obj-$(CONFIG_VFIO) += vfio.o > >> obj-$(CONFIG_VFIO_IOMMU_TYPE1) += vfio_iommu_type1.o > >> obj-$(CONFIG_VFIO_PCI) += pci/ > >> +obj-$(CONFIG_VFIO_PLATFORM) += vfio_platform.o > >> diff --git a/drivers/vfio/vfio_platform.c > b/drivers/vfio/vfio_platform.c new > > > > We can make this parallel to PCI, something like > drivers/vfio/platform/platform.c > > > pls, no. 'platform' is too generic, and it really means 'arm-dt' ... so > can > move it to the arch/arm space, and have it's kconfig conditional on > ARM&&VFIO. > if kept under drivers/vfio, then use a better directory name that ties it > to arm-dt. > thanks. This has nothing to do with ARM specifically. We need this for Power architecture as well. And the name should be 'platform' as that _is_ the name of the bus that these devices sit on. This has nothing to do with device tree's per se. It so happens that the device tree is parsed and devices discovered there are added to the platform bus. The intent is to allow devices on the platform bus to be passed through to user space using vfio. Stuart -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
