From: Chris Wright <chrisw@sous-sol.org>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Neil Horman <nhorman@redhat.com>,
Neil Horman <nhorman@tuxdriver.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Chris Wright <chrisw@sous-sol.org>,
hbabu@us.ibm.com, iommu@lists.linux-foundation.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Vivek Goyal <vgoyal@redhat.com>
Subject: [PATCH 1/2] x86/amd-iommu: enable iommu before attaching devices
Date: Thu, 1 Apr 2010 18:23:53 -0700 [thread overview]
Message-ID: <20100402012353.GY29241@sequoia.sous-sol.org> (raw)
In-Reply-To: <20100402003034.GX29241@sequoia.sous-sol.org>
Hit another kdump problem as reported by Neil Horman. When initializaing
the IOMMU, we attach devices to their domains before the IOMMU is
fully (re)initialized. Attaching a device will issue some important
invalidations. In the context of the newly kexec'd kdump kernel, the
IOMMU may have stale cached data from the original kernel. Because we
do the attach too early, the invalidation commands are placed in the new
command buffer before the IOMMU is updated w/ that buffer. This leaves
the stale entries in the kdump context and can renders device unusable.
Simply enable the IOMMU before we do the attach.
Cc: Neil Horman <nhorman@tuxdriver.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Chris Wright <chrisw@sous-sol.org>
---
arch/x86/kernel/amd_iommu_init.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/arch/x86/kernel/amd_iommu_init.c
+++ b/arch/x86/kernel/amd_iommu_init.c
@@ -1288,6 +1288,8 @@ static int __init amd_iommu_init(void)
if (ret)
goto free;
+ enable_iommus();
+
if (iommu_pass_through)
ret = amd_iommu_init_passthrough();
else
@@ -1300,8 +1302,6 @@ static int __init amd_iommu_init(void)
amd_iommu_init_notifier();
- enable_iommus();
-
if (iommu_pass_through)
goto out;
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-04-02 1:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 15:24 [PATCH] amd iommu: force flush of iommu prior during shutdown Neil Horman
2010-03-31 15:54 ` Vivek Goyal
2010-03-31 18:28 ` Neil Horman
2010-03-31 18:57 ` Eric W. Biederman
2010-03-31 19:18 ` Neil Horman
2010-03-31 19:51 ` Eric W. Biederman
2010-03-31 20:27 ` Neil Horman
2010-04-01 4:04 ` Eric W. Biederman
2010-04-01 12:49 ` Neil Horman
2010-04-01 14:29 ` Joerg Roedel
2010-04-01 14:47 ` Neil Horman
2010-04-01 15:56 ` Joerg Roedel
2010-04-01 17:11 ` Neil Horman
2010-04-01 20:14 ` Joerg Roedel
2010-04-02 0:00 ` Neil Horman
2010-04-02 0:30 ` Chris Wright
2010-04-02 1:23 ` Chris Wright [this message]
2010-04-02 1:31 ` [PATCH 2/2] x86/amd-iommu: warn when issuing command to uninitiailed cmd buffer Chris Wright
2010-04-02 1:35 ` [PATCH 1/2] x86/amd-iommu: enable iommu before attaching devices Neil Horman
2010-04-02 1:38 ` Chris Wright
2010-04-02 9:11 ` Joerg Roedel
2010-04-02 23:59 ` Chris Wright
2010-04-02 15:59 ` Vivek Goyal
2010-04-02 22:38 ` Chris Wright
2010-04-02 22:55 ` Eric W. Biederman
2010-04-02 23:57 ` Chris Wright
2010-04-03 17:38 ` Joerg Roedel
2010-04-05 14:17 ` Vivek Goyal
2010-04-05 14:32 ` Joerg Roedel
2010-04-05 15:34 ` Neil Horman
2010-03-31 18:43 ` [PATCH] amd iommu: force flush of iommu prior during shutdown Eric W. Biederman
2010-03-31 21:25 ` Chris Wright
2010-04-01 1:13 ` Neil Horman
2010-04-01 1:39 ` Chris Wright
2010-04-01 2:24 ` Vivek Goyal
2010-04-01 12:53 ` Neil Horman
2010-04-01 15:02 ` Vivek Goyal
2010-04-01 15:13 ` Neil Horman
2010-04-01 2:44 ` Vivek Goyal
2010-04-01 7:10 ` Chris Wright
2010-04-01 12:56 ` Neil Horman
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=20100402012353.GY29241@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=vgoyal@redhat.com \
/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