From: Christoph Hellwig <hch@lst.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux-foundation.org, x86@kernel.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>, Joerg Roedel <joro@8bytes.org>,
David Woodhouse <dwmw2@infradead.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org,
xen-devel@lists.xenproject.org, linux-ia64@vger.kernel.org,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org,
linux-hyperv@vger.kernel.org, tboot-devel@lists.sourceforge.net,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 07/11] x86: remove the IOMMU table infrastructure
Date: Wed, 2 Mar 2022 09:07:46 +0100 [thread overview]
Message-ID: <20220302080746.GA23075@lst.de> (raw)
In-Reply-To: <Yh5j5q5n/GyU0/1n@0xbeefdead.lan>
On Tue, Mar 01, 2022 at 01:20:22PM -0500, Konrad Rzeszutek Wilk wrote:
> I think you also need to check for IBM Calgary?
The IBM Calgary IOMMU support is long gone.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux-foundation.org, x86@kernel.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>, Joerg Roedel <joro@8bytes.org>,
David Woodhouse <dwmw2@infradead.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org,
xen-devel@lists.xenproject.org, linux-ia64@vger.kernel.org,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org,
linux-hyperv@vger.kernel.org, tboot-devel@lists.sourceforge.net,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 07/11] x86: remove the IOMMU table infrastructure
Date: Wed, 02 Mar 2022 08:07:46 +0000 [thread overview]
Message-ID: <20220302080746.GA23075@lst.de> (raw)
In-Reply-To: <Yh5j5q5n/GyU0/1n@0xbeefdead.lan>
On Tue, Mar 01, 2022 at 01:20:22PM -0500, Konrad Rzeszutek Wilk wrote:
> I think you also need to check for IBM Calgary?
The IBM Calgary IOMMU support is long gone.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Juergen Gross <jgross@suse.com>,
linux-s390@vger.kernel.org, linux-hyperv@vger.kernel.org,
Stefano Stabellini <sstabellini@kernel.org>,
linux-ia64@vger.kernel.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
x86@kernel.org, linux-mips@vger.kernel.org,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
iommu@lists.linux-foundation.org,
tboot-devel@lists.sourceforge.net, linux-pci@vger.kernel.org,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Woodhouse <dwmw2@infradead.org>,
Christoph Hellwig <hch@lst.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 07/11] x86: remove the IOMMU table infrastructure
Date: Wed, 2 Mar 2022 09:07:46 +0100 [thread overview]
Message-ID: <20220302080746.GA23075@lst.de> (raw)
In-Reply-To: <Yh5j5q5n/GyU0/1n@0xbeefdead.lan>
On Tue, Mar 01, 2022 at 01:20:22PM -0500, Konrad Rzeszutek Wilk wrote:
> I think you also need to check for IBM Calgary?
The IBM Calgary IOMMU support is long gone.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux-foundation.org, x86@kernel.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>, Joerg Roedel <joro@8bytes.org>,
David Woodhouse <dwmw2@infradead.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org,
xen-devel@lists.xenproject.org, linux-ia64@vger.kernel.org,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org,
linux-hyperv@vger.kernel.org, tboot-devel@lists.sourceforge.net,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 07/11] x86: remove the IOMMU table infrastructure
Date: Wed, 2 Mar 2022 09:07:46 +0100 [thread overview]
Message-ID: <20220302080746.GA23075@lst.de> (raw)
In-Reply-To: <Yh5j5q5n/GyU0/1n@0xbeefdead.lan>
On Tue, Mar 01, 2022 at 01:20:22PM -0500, Konrad Rzeszutek Wilk wrote:
> I think you also need to check for IBM Calgary?
The IBM Calgary IOMMU support is long gone.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Juergen Gross <jgross@suse.com>,
linux-s390@vger.kernel.org, linux-hyperv@vger.kernel.org,
Stefano Stabellini <sstabellini@kernel.org>,
linux-ia64@vger.kernel.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
x86@kernel.org, linux-mips@vger.kernel.org,
linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
iommu@lists.linux-foundation.org,
tboot-devel@lists.sourceforge.net, linux-pci@vger.kernel.org,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Woodhouse <dwmw2@infradead.org>,
Christoph Hellwig <hch@lst.de>,
linux-arm-kernel@lists.infradead.org,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH 07/11] x86: remove the IOMMU table infrastructure
Date: Wed, 2 Mar 2022 09:07:46 +0100 [thread overview]
Message-ID: <20220302080746.GA23075@lst.de> (raw)
In-Reply-To: <Yh5j5q5n/GyU0/1n@0xbeefdead.lan>
On Tue, Mar 01, 2022 at 01:20:22PM -0500, Konrad Rzeszutek Wilk wrote:
> I think you also need to check for IBM Calgary?
The IBM Calgary IOMMU support is long gone.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux-foundation.org, x86@kernel.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>, Joerg Roedel <joro@8bytes.org>,
David Woodhouse <dwmw2@infradead.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org,
xen-devel@lists.xenproject.org, linux-ia64@vger.kernel.org,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org,
linux-hyperv@vger.kernel.org, tboot-devel@lists.sourceforge.net,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 07/11] x86: remove the IOMMU table infrastructure
Date: Wed, 2 Mar 2022 09:07:46 +0100 [thread overview]
Message-ID: <20220302080746.GA23075@lst.de> (raw)
In-Reply-To: <Yh5j5q5n/GyU0/1n@0xbeefdead.lan>
On Tue, Mar 01, 2022 at 01:20:22PM -0500, Konrad Rzeszutek Wilk wrote:
> I think you also need to check for IBM Calgary?
The IBM Calgary IOMMU support is long gone.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-02 8:07 UTC|newest]
Thread overview: 130+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 14:30 cleanup swiotlb initialization v2 Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` [PATCH 01/11] dma-direct: use is_swiotlb_active in dma_direct_map_page Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` [PATCH 02/11] swiotlb: make swiotlb_exit a no-op if SWIOTLB_FORCE is set Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` [PATCH 03/11] swiotlb: simplify swiotlb_max_segment Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` [PATCH 04/11] swiotlb: rename swiotlb_late_init_with_default_size Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` [PATCH 05/11] swiotlb: pass a gfp_mask argument to swiotlb_init_late Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` [PATCH 06/11] MIPS/octeon: use swiotlb_init instead of open coding it Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` [PATCH 07/11] x86: remove the IOMMU table infrastructure Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-03-01 18:20 ` Konrad Rzeszutek Wilk
2022-03-01 18:20 ` Konrad Rzeszutek Wilk
2022-03-01 18:20 ` Konrad Rzeszutek Wilk
2022-03-01 18:20 ` Konrad Rzeszutek Wilk
2022-03-01 18:20 ` Konrad Rzeszutek Wilk
2022-03-01 18:20 ` Konrad Rzeszutek Wilk
2022-03-02 8:07 ` Christoph Hellwig [this message]
2022-03-02 8:07 ` Christoph Hellwig
2022-03-02 8:07 ` Christoph Hellwig
2022-03-02 8:07 ` Christoph Hellwig
2022-03-02 8:07 ` Christoph Hellwig
2022-03-02 8:07 ` Christoph Hellwig
2022-03-02 9:18 ` Anatoly Pugachev
2022-03-02 9:18 ` Anatoly Pugachev
2022-03-02 9:18 ` Anatoly Pugachev
2022-03-02 9:18 ` Anatoly Pugachev
2022-03-02 9:18 ` Anatoly Pugachev
2022-03-02 9:18 ` Anatoly Pugachev
2022-03-02 9:22 ` Christoph Hellwig
2022-03-02 9:22 ` Christoph Hellwig
2022-03-02 9:22 ` Christoph Hellwig
2022-03-02 9:22 ` Christoph Hellwig
2022-03-02 9:22 ` Christoph Hellwig
2022-03-02 9:22 ` Christoph Hellwig
2022-02-27 14:30 ` [PATCH 08/11] swiotlb: make the swiotlb_init interface more useful Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 18:15 ` Christophe Leroy
2022-02-27 18:15 ` Christophe Leroy
2022-02-27 18:15 ` Christophe Leroy
2022-02-27 18:15 ` Christophe Leroy
2022-02-27 18:15 ` Christophe Leroy
2022-02-27 18:15 ` Christophe Leroy
2022-02-28 2:53 ` Michael Kelley (LINUX)
2022-02-28 2:53 ` Michael Kelley (LINUX)
2022-02-28 2:53 ` Michael Kelley (LINUX)
2022-02-28 2:53 ` Michael Kelley (LINUX)
2022-02-28 2:53 ` Michael Kelley (LINUX) via iommu
2022-02-28 11:30 ` Christoph Hellwig
2022-02-28 11:30 ` Christoph Hellwig
2022-02-28 11:30 ` Christoph Hellwig
2022-02-28 11:30 ` Christoph Hellwig
2022-02-28 11:30 ` Christoph Hellwig
2022-02-28 11:30 ` Christoph Hellwig
2022-02-28 17:21 ` Michael Kelley (LINUX)
2022-02-28 17:21 ` Michael Kelley (LINUX)
2022-02-28 17:21 ` Michael Kelley (LINUX)
2022-02-28 17:21 ` Michael Kelley (LINUX)
2022-02-28 17:21 ` Michael Kelley (LINUX) via iommu
2022-02-27 14:30 ` [PATCH 09/11] swiotlb: add a SWIOTLB_ANY flag to lift the low memory restriction Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` [PATCH 10/11] swiotlb: merge swiotlb-xen initialization into swiotlb Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` [PATCH 11/11] x86: remove cruft from <asm/dma-mapping.h> Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
2022-02-27 14:30 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2022-02-22 15:35 cleanup swiotlb initialization Christoph Hellwig
2022-02-22 15:35 ` [PATCH 07/11] x86: remove the IOMMU table infrastructure Christoph Hellwig
2022-02-22 15:35 ` Christoph Hellwig
2022-02-22 15:35 ` Christoph Hellwig
2022-02-22 15:35 ` Christoph Hellwig
2022-02-22 15:35 ` Christoph Hellwig
2022-02-22 15:35 ` Christoph Hellwig
2022-02-24 10:18 ` Anshuman Khandual
2022-02-24 10:30 ` Anshuman Khandual
2022-02-24 10:18 ` Anshuman Khandual
2022-02-24 10:18 ` Anshuman Khandual
2022-02-24 10:18 ` Anshuman Khandual
2022-02-24 10:18 ` Anshuman Khandual
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=20220302080746.GA23075@lst.de \
--to=hch@lst.de \
--cc=anshuman.khandual@arm.com \
--cc=baolu.lu@linux.intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jgross@suse.com \
--cc=joro@8bytes.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robin.murphy@arm.com \
--cc=sstabellini@kernel.org \
--cc=tboot-devel@lists.sourceforge.net \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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.