From: Dave Young <dyoung@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: luyu@redhat.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
horms@verge.net.au, vgoyal@redhat.com
Subject: Re: [PATCH retry] intel-iommu:make identity_map default for crash dump
Date: Tue, 01 Nov 2011 17:52:28 +0800 [thread overview]
Message-ID: <4EAFC15C.7010601@redhat.com> (raw)
In-Reply-To: <1320140052.2089.5.camel@shinybook.infradead.org>
On 11/01/2011 05:34 PM, David Woodhouse wrote:
> On Tue, 2011-11-01 at 17:19 +0800, Dave Young wrote:
>> kdump kernel sometimes will get DMAR faults which
>> is caused by random in-flight dma from 1st kernel
>>
>> Here make the identity_mapping as default for this case
>
> So you want to *allow* the random in-flight DMA? And with an identity
> mapping it's really going to random addresses, since it'll be
> untranslated and won't even go to the physical addresses which it was
> originally intended for?
>
> This seems entirely broken to me.
>
> If there is "random in-flight dma" from the first kernel, the correct
> thing to do is *block* it. Which is what we do.
>
This patch works for me for several cases. For kdump It can be seen a
workaround. But yes blocking the 1st kernel dma is ideal.
Glad to hear that you are working on this.
--
Thanks
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2011-11-01 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 9:19 [PATCH retry] intel-iommu:make identity_map default for crash dump Dave Young
2011-11-01 9:34 ` David Woodhouse
2011-11-01 9:52 ` Dave Young [this message]
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=4EAFC15C.7010601@redhat.com \
--to=dyoung@redhat.com \
--cc=dwmw2@infradead.org \
--cc=horms@verge.net.au \
--cc=iommu@lists.linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luyu@redhat.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