From: Simon Horman <horms@verge.net.au>
To: Dave Young <dyoung@redhat.com>
Cc: iommu@lists.linux-foundation.org, luyu@redhat.com,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
vgoyal@redhat.com
Subject: Re: [PATCH] intel-iommu:make identity_map default for crash dump
Date: Sat, 22 Oct 2011 10:08:21 +0900 [thread overview]
Message-ID: <20111022010821.GF21850@verge.net.au> (raw)
In-Reply-To: <20111021123154.GA5821@darkstar.nay.redhat.com>
On Fri, Oct 21, 2011 at 08:31:54PM +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
This seems reasonable to me. Although I am curious to know
what the side effects of using IDENTMAP_ALL might be.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: Dave Young <dyoung@redhat.com>
Cc: kexec@lists.infradead.org, iommu@lists.linux-foundation.org,
vgoyal@redhat.com, linux-kernel@vger.kernel.org, luyu@redhat.com
Subject: Re: [PATCH] intel-iommu:make identity_map default for crash dump
Date: Sat, 22 Oct 2011 10:08:21 +0900 [thread overview]
Message-ID: <20111022010821.GF21850@verge.net.au> (raw)
In-Reply-To: <20111021123154.GA5821@darkstar.nay.redhat.com>
On Fri, Oct 21, 2011 at 08:31:54PM +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
This seems reasonable to me. Although I am curious to know
what the side effects of using IDENTMAP_ALL might be.
next prev parent reply other threads:[~2011-10-22 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 12:31 [PATCH] intel-iommu:make identity_map default for crash dump Dave Young
2011-10-21 12:31 ` Dave Young
2011-10-22 1:08 ` Simon Horman [this message]
2011-10-22 1:08 ` Simon 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=20111022010821.GF21850@verge.net.au \
--to=horms@verge.net.au \
--cc=dyoung@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.