From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Will Deacon <will@kernel.org>
Cc: Ashok Raj <ashok.raj@intel.com>,
catalin.marinas@arm.com, x86@kernel.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Ning Sun <ning.sun@intel.com>,
tboot-devel@lists.sourceforge.net, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Adrian Huang <ahuang12@lenovo.com>,
Thomas Gleixner <tglx@linutronix.de>,
kernel-team@android.com
Subject: Re: [PATCH 1/1] x86/tboot: Don't disable swiotlb when iommu is forced on
Date: Wed, 25 Nov 2020 10:41:53 -0500 [thread overview]
Message-ID: <20201125154153.GA29929@localhost.localdomain> (raw)
In-Reply-To: <160630605367.4096500.10722779964348157570.b4-ty@kernel.org>
On Wed, Nov 25, 2020 at 02:05:15PM +0000, Will Deacon wrote:
> On Wed, 25 Nov 2020 09:41:24 +0800, Lu Baolu wrote:
> > After commit 327d5b2fee91c ("iommu/vt-d: Allow 32bit devices to uses DMA
> > domain"), swiotbl could also be used for direct memory access if IOMMU
> > is enabled but a device is configured to pass through the DMA translation.
> > Keep swiotlb when IOMMU is forced on, otherwise, some devices won't work
> > if "iommu=pt" kernel parameter is used.
>
> Applied to arm64 (for-next/iommu/fixes), thanks!
>
> [1/1] x86/tboot: Don't disable swiotlb when iommu is forced on
> https://git.kernel.org/arm64/c/e2be2a833ab5
But tboot never ran on ARM. It is a Intel specifc.
I think either me or Thomas should take this patch.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-11-25 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 1:41 [PATCH 1/1] x86/tboot: Don't disable swiotlb when iommu is forced on Lu Baolu
2020-11-25 14:05 ` Will Deacon
2020-11-25 15:41 ` Konrad Rzeszutek Wilk [this message]
2020-11-25 15:51 ` Will Deacon
2020-11-25 16:25 ` Konrad Rzeszutek Wilk
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=20201125154153.GA29929@localhost.localdomain \
--to=konrad@darnok.org \
--cc=ahuang12@lenovo.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ning.sun@intel.com \
--cc=tboot-devel@lists.sourceforge.net \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).