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.5-rc6
Date: Thu, 3 Mar 2016 14:51:51 +0100 [thread overview]
Message-ID: <20160303135151.GA30025@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
Hi Linus,
The following changes since commit 81f70ba233d5f660e1ea5fe23260ee323af5d53a:
Linux 4.5-rc5 (2016-02-20 13:39:35 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.5-rc6
for you to fetch changes up to e6a8c9b337eed56eb481e1b4dd2180c25a1e5310:
iommu/vt-d: Use BUS_NOTIFY_REMOVED_DEVICE in hotplug path (2016-02-29 23:55:16 +0100)
----------------------------------------------------------------
IOMMU Fixes for Linux v4.5-rc6
Including one fix for Intel VT-d:
* Use BUS_NOTIFY_REMOVED_DEVICE notifier to unbind a device from
its domain _after_ it has been unbound from its driver. This
fixes a BUG_ON being triggered in the PCI hotplug path.
And three for AMD IOMMU:
* Add a workaround for a hardware issue with ATS in use
* Fix ATS enable/disable balance when a device is removed
* Fix a boot warning being triggered when the system has IOMMU
performance counters and PCI device 00:00.0 is not covered by
the IOMMU
----------------------------------------------------------------
Jay Cornwall (1):
iommu/amd: Apply workaround for ATS write permission check
Joerg Roedel (2):
iommu/amd: Detach device from domain before removal
iommu/vt-d: Use BUS_NOTIFY_REMOVED_DEVICE in hotplug path
Suravee Suthikulpanit (1):
iommu/amd: Fix boot warning when device 00:00.0 is not iommu covered
drivers/iommu/amd_iommu.c | 4 +++
drivers/iommu/amd_iommu_init.c | 63 ++++++++++++++++++++++++++++++++++--------
drivers/iommu/dmar.c | 5 ++--
drivers/iommu/intel-iommu.c | 4 +--
4 files changed, 60 insertions(+), 16 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2016-03-03 13: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=20160303135151.GA30025@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