From: Jason Gunthorpe <jgg@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: joro@8bytes.org, will@kernel.org, catalin.marinas@arm.com,
jean-philippe@linaro.org, inki.dae@samsung.com,
sw0312.kim@samsung.com, kyungmin.park@samsung.com,
tglx@linutronix.de, maz@kernel.org, alex.williamson@redhat.com,
cohuck@redhat.com, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH 1/3] iommu/dma: Clean up Kconfig
Date: Fri, 5 May 2023 16:22:34 -0300 [thread overview]
Message-ID: <ZFVXeoNsa0w8KoJm@nvidia.com> (raw)
In-Reply-To: <8eab6d63-1fa1-704f-279b-83b2df7fa808@arm.com>
On Fri, May 05, 2023 at 03:53:54PM +0100, Robin Murphy wrote:
> > > diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
> > > index 5c5cb5bee8b6..1d99c2d984fb 100644
> > > --- a/drivers/iommu/Kconfig
> > > +++ b/drivers/iommu/Kconfig
> > > @@ -137,7 +137,7 @@ config OF_IOMMU
> > > # IOMMU-agnostic DMA-mapping layer
> > > config IOMMU_DMA
> > > - bool
> > > + def_bool ARM64 || IA64 || X86
> >
> > Robin, do you remember why you added IA64 here? What is the Itanimum
> > IOMMU driver?
>
> config INTEL_IOMMU
> bool "Support for Intel IOMMU using DMA Remapping Devices"
> depends on PCI_MSI && ACPI && (X86 || IA64)
>
> Yes, really :)
Wowo, thanks!
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: joro@8bytes.org, will@kernel.org, catalin.marinas@arm.com,
jean-philippe@linaro.org, inki.dae@samsung.com,
sw0312.kim@samsung.com, kyungmin.park@samsung.com,
tglx@linutronix.de, maz@kernel.org, alex.williamson@redhat.com,
cohuck@redhat.com, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH 1/3] iommu/dma: Clean up Kconfig
Date: Fri, 5 May 2023 16:22:34 -0300 [thread overview]
Message-ID: <ZFVXeoNsa0w8KoJm@nvidia.com> (raw)
In-Reply-To: <8eab6d63-1fa1-704f-279b-83b2df7fa808@arm.com>
On Fri, May 05, 2023 at 03:53:54PM +0100, Robin Murphy wrote:
> > > diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
> > > index 5c5cb5bee8b6..1d99c2d984fb 100644
> > > --- a/drivers/iommu/Kconfig
> > > +++ b/drivers/iommu/Kconfig
> > > @@ -137,7 +137,7 @@ config OF_IOMMU
> > > # IOMMU-agnostic DMA-mapping layer
> > > config IOMMU_DMA
> > > - bool
> > > + def_bool ARM64 || IA64 || X86
> >
> > Robin, do you remember why you added IA64 here? What is the Itanimum
> > IOMMU driver?
>
> config INTEL_IOMMU
> bool "Support for Intel IOMMU using DMA Remapping Devices"
> depends on PCI_MSI && ACPI && (X86 || IA64)
>
> Yes, really :)
Wowo, thanks!
Jason
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: jean-philippe@linaro.org, kvm@vger.kernel.org,
iommu@lists.linux.dev, catalin.marinas@arm.com, joro@8bytes.org,
cohuck@redhat.com, sw0312.kim@samsung.com,
alex.williamson@redhat.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
kyungmin.park@samsung.com, maz@kernel.org, tglx@linutronix.de,
will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] iommu/dma: Clean up Kconfig
Date: Fri, 5 May 2023 16:22:34 -0300 [thread overview]
Message-ID: <ZFVXeoNsa0w8KoJm@nvidia.com> (raw)
In-Reply-To: <8eab6d63-1fa1-704f-279b-83b2df7fa808@arm.com>
On Fri, May 05, 2023 at 03:53:54PM +0100, Robin Murphy wrote:
> > > diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
> > > index 5c5cb5bee8b6..1d99c2d984fb 100644
> > > --- a/drivers/iommu/Kconfig
> > > +++ b/drivers/iommu/Kconfig
> > > @@ -137,7 +137,7 @@ config OF_IOMMU
> > > # IOMMU-agnostic DMA-mapping layer
> > > config IOMMU_DMA
> > > - bool
> > > + def_bool ARM64 || IA64 || X86
> >
> > Robin, do you remember why you added IA64 here? What is the Itanimum
> > IOMMU driver?
>
> config INTEL_IOMMU
> bool "Support for Intel IOMMU using DMA Remapping Devices"
> depends on PCI_MSI && ACPI && (X86 || IA64)
>
> Yes, really :)
Wowo, thanks!
Jason
next prev parent reply other threads:[~2023-05-05 19:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 17:28 [PATCH 0/3] iommu/dma: Some housekeeping Robin Murphy
2022-08-16 17:28 ` Robin Murphy
2022-08-16 17:28 ` Robin Murphy
2022-08-16 17:28 ` [PATCH 1/3] iommu/dma: Clean up Kconfig Robin Murphy
2022-08-16 17:28 ` Robin Murphy
2022-08-16 17:28 ` Robin Murphy
2022-09-02 18:15 ` Catalin Marinas
2022-09-02 18:15 ` Catalin Marinas
2022-09-02 18:15 ` Catalin Marinas
2023-05-05 14:50 ` Jason Gunthorpe
2023-05-05 14:50 ` Jason Gunthorpe
2023-05-05 14:50 ` Jason Gunthorpe
2023-05-05 14:53 ` Robin Murphy
2023-05-05 14:53 ` Robin Murphy
2023-05-05 14:53 ` Robin Murphy
2023-05-05 19:22 ` Jason Gunthorpe [this message]
2023-05-05 19:22 ` Jason Gunthorpe
2023-05-05 19:22 ` Jason Gunthorpe
2022-08-16 17:28 ` [PATCH 2/3] iommu/dma: Move public interfaces to linux/iommu.h Robin Murphy
2022-08-16 17:28 ` Robin Murphy
2022-08-16 17:28 ` Robin Murphy
2022-08-17 12:19 ` Marc Zyngier
2022-08-17 12:19 ` Marc Zyngier
2022-08-17 12:19 ` Marc Zyngier
2022-08-22 11:21 ` Christoph Hellwig
2022-08-22 11:21 ` Christoph Hellwig
2022-08-22 12:55 ` Robin Murphy
2022-08-22 12:55 ` Robin Murphy
2022-08-22 12:55 ` Robin Murphy
2022-09-02 18:16 ` Catalin Marinas
2022-09-02 18:16 ` Catalin Marinas
2022-09-02 18:16 ` Catalin Marinas
2022-08-16 17:28 ` [PATCH 3/3] iommu/dma: Make header private Robin Murphy
2022-08-16 17:28 ` Robin Murphy
2022-08-16 17:28 ` Robin Murphy
2022-09-07 12:49 ` [PATCH 0/3] iommu/dma: Some housekeeping Joerg Roedel
2022-09-07 12:49 ` Joerg Roedel
2022-09-07 12:49 ` Joerg Roedel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZFVXeoNsa0w8KoJm@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=cohuck@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sw0312.kim@samsung.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.