Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756683AbaKTOK7 (ORCPT ); Thu, 20 Nov 2014 09:10:59 -0500 Received: from mail-pd0-f176.google.com ([209.85.192.176]:37641 "EHLO mail-pd0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756498AbaKTOK4 (ORCPT ); Thu, 20 Nov 2014 09:10:56 -0500 MIME-Version: 1.0 X-Originating-IP: [2a01:e35:2434:4600:224:8cff:fe66:7f7e] In-Reply-To: References: <1414433284-31719-1-git-send-email-a.motakis@virtualopensystems.com> <1414433284-31719-4-git-send-email-a.motakis@virtualopensystems.com> From: Antonios Motakis Date: Thu, 20 Nov 2014 15:10:35 +0100 Message-ID: Subject: Re: [PATCH v9 03/19] vfio: platform: add the VFIO PLATFORM module to Kconfig To: Hongbo Zhang Cc: kvm-arm , Linux IOMMU , Alex Williamson , Will Deacon , VirtualOpenSystems Technical Team , Christoffer Dall , Eric Auger , Kim Phillips , Marc Zyngier , open list , "open list:VFIO DRIVER" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 13, 2014 at 9:05 AM, Hongbo Zhang wrote: > On 12 November 2014 17:57, Antonios Motakis > wrote: >> Hello Hongbo, >> >> On Wed, Nov 12, 2014 at 10:52 AM, Hongbo Zhang wrote: >>> On 28 October 2014 02:07, Antonios Motakis >>> wrote: >>>> >>>> Enable building the VFIO PLATFORM driver that allows to use Linux platform >>>> devices with VFIO. >>>> >>>> Signed-off-by: Antonios Motakis >>>> --- >>>> drivers/vfio/Kconfig | 1 + >>>> drivers/vfio/Makefile | 1 + >>>> drivers/vfio/platform/Kconfig | 9 +++++++++ >>>> drivers/vfio/platform/Makefile | 4 ++++ >>>> 4 files changed, 15 insertions(+) >>>> create mode 100644 drivers/vfio/platform/Kconfig >>>> create mode 100644 drivers/vfio/platform/Makefile >>>> >>>> diff --git a/drivers/vfio/Kconfig b/drivers/vfio/Kconfig >>>> index a0abe04..962fb80 100644 >>>> --- a/drivers/vfio/Kconfig >>>> +++ b/drivers/vfio/Kconfig >>>> @@ -27,3 +27,4 @@ menuconfig VFIO >>>> If you don't know what to do here, say N. >>>> >>>> source "drivers/vfio/pci/Kconfig" >>>> +source "drivers/vfio/platform/Kconfig" >>>> diff --git a/drivers/vfio/Makefile b/drivers/vfio/Makefile >>>> index 0b035b1..dadf0ca 100644 >>>> --- a/drivers/vfio/Makefile >>>> +++ b/drivers/vfio/Makefile >>>> @@ -3,3 +3,4 @@ obj-$(CONFIG_VFIO_IOMMU_TYPE1) += vfio_iommu_type1.o >>>> obj-$(CONFIG_VFIO_IOMMU_SPAPR_TCE) += vfio_iommu_spapr_tce.o >>>> obj-$(CONFIG_VFIO_SPAPR_EEH) += vfio_spapr_eeh.o >>>> obj-$(CONFIG_VFIO_PCI) += pci/ >>>> +obj-$(CONFIG_VFIO_PLATFORM) += platform/ >>>> diff --git a/drivers/vfio/platform/Kconfig b/drivers/vfio/platform/Kconfig >>>> new file mode 100644 >>>> index 0000000..c51af17 >>>> --- /dev/null >>>> +++ b/drivers/vfio/platform/Kconfig >>>> @@ -0,0 +1,9 @@ >>>> +config VFIO_PLATFORM >>>> + tristate "VFIO support for platform devices" >>>> + depends on VFIO && EVENTFD && ARM >>> >>> Hi Antonios, >>> Is this only for ARM? how about X86 and PowerPC? >>> On Freescale's PowerPC platform, the IOMMU is called PAMU (Peripheral >>> Access Management Unit), and I am trying to use this VFIO framework on >>> it. >>> >> >> In principle it should be working on any platform with such devices; >> as long as you have a VFIO IOMMU driver for the PAMU (on ARM we use >> VFIO PLATFORM for the device, with VFIO IOMMU TYPE1 for the IOMMU). >> > > Antonios, > As far as you know, on which ARM platform can I apply your patches directly? > My purpose is to apply you patches[1], and then implement a user space > driver to evaluate the performance. > In principle, if your target has a working IOMMU in front of a platform or AMBA device, then you should be able to use this. In practice, I have tested this on various fast models, and less extensively on Arndale in the past. Linaro as far as I know has tested this series on Calxeda devices with an xgmac NIC. > [1] It is better without manually merging conflicts/dependencies etc, > I am vfio-platform user, not a iommu expert. > >> So if you have a suitable IOMMU driver for your target, feel free to >> test it, and let us know of the results. >> >>>> >>>> + help >>>> + Support for platform devices with VFIO. This is required to make >>>> + use of platform devices present on the system using the VFIO >>>> + framework. >>>> + >>>> + If you don't know what to do here, say N. >>>> diff --git a/drivers/vfio/platform/Makefile b/drivers/vfio/platform/Makefile >>>> new file mode 100644 >>>> index 0000000..279862b >>>> --- /dev/null >>>> +++ b/drivers/vfio/platform/Makefile >>>> @@ -0,0 +1,4 @@ >>>> + >>>> +vfio-platform-y := vfio_platform.o vfio_platform_common.o >>>> + >>>> +obj-$(CONFIG_VFIO_PLATFORM) += vfio-platform.o >>>> -- >>>> 2.1.1 >>>> >>>> -- >>>> 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/ -- 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/