From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [git pull] IOMMU Fixes for Linux v4.14-rc4
Date: Fri, 13 Oct 2017 17:51:57 +0200 [thread overview]
Message-ID: <20171013155153.lo3mqqf46zav4jhg@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
Hi Linus,
The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f:
Linux 4.14-rc4 (2017-10-08 20:53:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.14-rc4
for you to fetch changes up to ce76353f169a6471542d999baf3d29b121dce9c0:
iommu/amd: Finish TLB flush in amd_iommu_unmap() (2017-10-13 17:32:19 +0200)
----------------------------------------------------------------
IOMMU Fixes for Linux v4.14-rc4
Three fixes:
- Keep an important data structure in the Exynos driver around
after kernel-init to fix a kernel-oops
- Keep SWIOTLB enabled when SME is active in the AMD IOMMU
driver
- Add a missing IOTLB sync to the AMD IOMMU driver
----------------------------------------------------------------
Joerg Roedel (1):
iommu/amd: Finish TLB flush in amd_iommu_unmap()
Marek Szyprowski (1):
iommu/exynos: Remove initconst attribute to avoid potential kernel oops
Tom Lendacky (1):
iommu/amd: Do not disable SWIOTLB if SME is active
drivers/iommu/amd_iommu.c | 11 +++++++----
drivers/iommu/exynos-iommu.c | 2 +-
2 files changed, 8 insertions(+), 5 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2017-10-13 15:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171013155153.lo3mqqf46zav4jhg@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).