| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAOhR-w2R-6zwqXULHeyx3v+CDBJX9LDDeySsfd4ix3f0hd1f=w@mail.gmail.com> Date: Wed, 12 Nov 2014 19:17:17 +0800 From: Hongbo Zhang <hongbo.zhang@...aro.org> To: "Bharat.Bhushan@...escale.com" <Bharat.Bhushan@...escale.com> Cc: Antonios Motakis <a.motakis@...tualopensystems.com>, "open list:VFIO DRIVER" <kvm@...r.kernel.org>, "will.deacon@....com" <will.deacon@....com>, "alex.williamson@...hat.com" <alex.williamson@...hat.com>, open list <linux-kernel@...r.kernel.org>, "iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>, "tech@...tualopensystems.com" <tech@...tualopensystems.com>, "kvmarm@...ts.cs.columbia.edu" <kvmarm@...ts.cs.columbia.edu> Subject: Re: [PATCH v9 03/19] vfio: platform: add the VFIO PLATFORM module to Kconfig On 12 November 2014 19:00, Bharat.Bhushan@...escale.com <Bharat.Bhushan@...escale.com> wrote: > > >> -----Original Message----- >> From: Hongbo Zhang [mailto:hongbo.zhang@...aro.org] >> Sent: Wednesday, November 12, 2014 4:09 PM >> To: Bhushan Bharat-R65777 >> Cc: Antonios Motakis; open list:VFIO DRIVER; will.deacon@....com; >> alex.williamson@...hat.com; open list; iommu@...ts.linux-foundation.org; >> tech@...tualopensystems.com; kvmarm@...ts.cs.columbia.edu >> Subject: Re: [PATCH v9 03/19] vfio: platform: add the VFIO PLATFORM module to >> Kconfig >> >> On 12 November 2014 18:05, Bharat.Bhushan@...escale.com >> <Bharat.Bhushan@...escale.com> wrote: >> > Hi, >> > >> > >> > >> > This is not yet supported on Freescale PowerPC. I am still in process >> > of upstreaming the FSL PAMU specific patches for same. >> > >> > Initial plan is to test with PCIe devices and then with Platform devices. >> > >> >> I see there is already driver/iommu/fsl_pamu.c, doesn't it work? > > We need VFIO iommu driver for same. > >> Could you explain briefly what is wrong? I've heard that the vfio pci works on >> powerpc platforms. > > Yes, patches are in Freescale internal git repository. But those patches are yet to be upstreamed. I have started working on same. (I come from Freescale too, just currently assigned to Linaro) Oh, yes I now see vfio iommu driver in the internal git repo, but not in the community one. It seems I have to select another platform within Linaro to work with. > > Thanks > -Bharat > >> >> > >> > >> > Thanks >> > >> > -Bharat >> > >> > >> > >> > From: kvmarm-bounces@...ts.cs.columbia.edu >> > [mailto:kvmarm-bounces@...ts.cs.columbia.edu] On Behalf Of Hongbo >> > Zhang >> > Sent: Wednesday, November 12, 2014 3:08 PM >> > To: Antonios Motakis >> > Cc: open list:VFIO DRIVER; will.deacon@....com; >> > alex.williamson@...hat.com; open list; >> > iommu@...ts.linux-foundation.org; tech@...tualopensystems.com; >> > kvmarm@...ts.cs.columbia.edu >> > Subject: Re: [PATCH v9 03/19] vfio: platform: add the VFIO PLATFORM >> > module to Kconfig >> > >> > >> > >> > >> > >> > >> > >> > On 28 October 2014 02:07, Antonios Motakis >> > <a.motakis@...tualopensystems.com> wrote: >> > >> > Enable building the VFIO PLATFORM driver that allows to use Linux >> > platform devices with VFIO. >> > >> > Signed-off-by: Antonios Motakis <a.motakis@...tualopensystems.com> >> > --- >> > 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. >> > >> > >> > >> > + 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@...r.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@...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