From: Joerg Roedel <joerg.roedel@amd.com>
To: Ingo Molnar <mingo@redhat.com>, <x86@kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] AMD IOMMU updates for 2.6.37
Date: Wed, 13 Oct 2010 14:36:02 +0200 [thread overview]
Message-ID: <1286973364-17077-1-git-send-email-joerg.roedel@amd.com> (raw)
Hi Ingo,
The following changes since commit 899611ee7d373e5eeda08e9a8632684e1ebbbf00:
Linus Torvalds (1):
Linux 2.6.36-rc6
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/linux-2.6-iommu.git amd-iommu/2.6.37
Joerg Roedel (1):
x86/amd-iommu: Update copyright headers
Matthew Garrett (1):
x86/amd-iommu: Reenable AMD IOMMU if it's mysteriously vanished over suspend
arch/x86/include/asm/amd_iommu.h | 2 +-
arch/x86/include/asm/amd_iommu_proto.h | 2 +-
arch/x86/include/asm/amd_iommu_types.h | 23 ++++--
arch/x86/kernel/amd_iommu.c | 2 +-
arch/x86/kernel/amd_iommu_init.c | 124 ++++++++++++++++++++++++++++----
5 files changed, 128 insertions(+), 25 deletions(-)
This update is mostly about a workaround for BIOS problems with AMD IOMMU when
resuming from S3. The BIOS on an AMD IOMMU capable machine might be buggy so
that the IOMMU device is not re-enabled on resume. The patch from Matthew
implement a workaround for this problem by manually re-enabling an
re-programming the IOMMU device on resume. Please pull.
Joerg
next reply other threads:[~2010-10-13 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 12:36 Joerg Roedel [this message]
2010-10-13 12:36 ` [PATCH 1/2] x86/amd-iommu: Reenable AMD IOMMU if it's mysteriously vanished over suspend Joerg Roedel
2010-10-13 12:36 ` [PATCH 2/2] x86/amd-iommu: Update copyright headers Joerg Roedel
2010-10-13 13:45 ` [GIT PULL] AMD IOMMU updates for 2.6.37 Ingo Molnar
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=1286973364-17077-1-git-send-email-joerg.roedel@amd.com \
--to=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
Powered by JetHome