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 3.5-rc1
Date: Wed, 6 Jun 2012 15:56:32 +0200 [thread overview]
Message-ID: <20120606135632.GA4196@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
Hi Linus,
The following changes since commit f8f5701bdaf9134b1f90e5044a82c66324d2073f:
Linux 3.5-rc1 (2012-06-02 18:29:26 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-3.5-rc1
for you to fetch changes up to eee53537c476c947bf7faa1c916d2f5a0ae8ec93:
iommu/amd: Fix deadlock in ppr-handling error path (2012-06-04 12:47:44 +0200)
----------------------------------------------------------------
IOMMU fixes for v3.5-rc1
Two patches are in here which fix AMD IOMMU specific issues. One patch
fixes a long-standing warning on resume because the amd_iommu_resume
function enabled interrupts. The other patch fixes a deadlock in an
error-path of the page-fault request handling code of the IOMMU driver.
----------------------------------------------------------------
Joerg Roedel (2):
iommu/amd: Cache pdev pointer to root-bridge
iommu/amd: Fix deadlock in ppr-handling error path
drivers/iommu/amd_iommu.c | 71 ++++++++++++++++++++++++---------------
drivers/iommu/amd_iommu_init.c | 13 +++----
drivers/iommu/amd_iommu_types.h | 3 ++
3 files changed, 52 insertions(+), 35 deletions(-)
Please pull.
Regards,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-06-06 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 13:56 Joerg Roedel [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-02 13:09 [git pull] IOMMU fixes for Linux 3.5-rc1 Joerg Roedel
[not found] ` <20120702130910.GA12232-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2012-07-02 13:17 ` 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=20120606135632.GA4196@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).