From: Dave Young <dyoung@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Baoquan He <bhe@redhat.com>, "Li, ZhenHua" <zhen-hual@hp.com>,
dwmw2@infradead.org, indou.takao@jp.fujitsu.com,
vgoyal@redhat.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
kexec@lists.infradead.org, alex.williamson@redhat.com,
ddutile@redhat.com, ishii.hironobu@jp.fujitsu.com,
bhelgaas@google.com, doug.hatch@hp.com, jerry.hoemann@hp.com,
tom.vaden@hp.com, li.zhang6@hp.com, lisa.mitchell@hp.com,
billsumnerlinux@gmail.com, rwright@hp.com
Subject: Re: [PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel
Date: Tue, 5 May 2015 14:14:23 +0800 [thread overview]
Message-ID: <20150505061423.GC31063@dhcp-128-4.nay.redhat.com> (raw)
In-Reply-To: <20150504162318.GH15736@8bytes.org>
On 05/04/15 at 06:23pm, Joerg Roedel wrote:
> On Fri, Apr 24, 2015 at 04:49:57PM +0800, Dave Young wrote:
> > I'm more than happy to see this issue can be fixed in the patchset, I
> > do not agree to add the code there with such problems. OTOH, for now
> > seems there's no way to fix it.
>
> And that's the point. We discuss this issue and possible solutions for
> years by now, and what ZhenHua implemented is what we agreed to be the
> best-effort on what we can do in the kdump case with IOMMU enabled.
>
> Of course there are still failure scenarios left, but that is not
> different from systems without any IOMMU.
The failure is nothing different, but as I said in another reply the
difference is we could use corrupted data to possiblly cause more failure.
Thanks
Dave
next prev parent reply other threads:[~2015-05-05 6:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 8:42 [PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel Li, Zhen-Hua
[not found] ` <1428655333-19504-1-git-send-email-zhen-hual-VXdhtT5mjnY@public.gmane.org>
2015-04-10 8:42 ` [PATCH v10 01/10] iommu/vt-d: New function to attach domain with id Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 02/10] iommu/vt-d: Items required for kdump Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 03/10] iommu/vt-d: Function to get old context entry Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 04/10] iommu/vt-d: functions to copy data from old mem Li, Zhen-Hua
2015-05-07 7:49 ` Baoquan He
[not found] ` <20150507074916.GA16815-je1gSBvt1Tcx0jIIkfS+Ph/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2015-05-07 8:33 ` Li, ZhenHua
2015-04-10 8:42 ` [PATCH v10 05/10] iommu/vt-d: Add functions to load and save old re Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 06/10] iommu/vt-d: datatypes and functions used for kdump Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 07/10] iommu/vt-d: enable kdump support in iommu module Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 08/10] iommu/vt-d: assign new page table for dma_map Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 09/10] iommu/vt-d: Copy functions for irte Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 10/10] iommu/vt-d: Use old irte in kdump kernel Li, Zhen-Hua
2015-04-23 8:35 ` [PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults " Li, ZhenHua
[not found] ` <5538AEC4.8030307-VXdhtT5mjnY@public.gmane.org>
2015-04-23 8:38 ` Li, ZhenHua
2015-04-29 11:20 ` Baoquan He
[not found] ` <20150429112024.GB5799-je1gSBvt1Tcx0jIIkfS+Ph/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2015-05-03 8:55 ` Baoquan He
[not found] ` <20150503085530.GK15033-je1gSBvt1Tcx0jIIkfS+Ph/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2015-05-04 3:06 ` Li, ZhenHua
2015-05-04 3:17 ` Baoquan He
[not found] ` <20150504031749.GF5799-je1gSBvt1Tcx0jIIkfS+Ph/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2015-05-07 17:32 ` Joerg Roedel
[not found] ` <20150507173200.GF20611-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-05-08 1:00 ` Li, ZhenHua
2015-04-15 0:57 ` Dave Young
[not found] ` <20150415005731.GC19051-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-04-15 5:47 ` Li, ZhenHua
2015-04-15 6:48 ` Dave Young
2015-04-21 1:39 ` Li, ZhenHua
[not found] ` <5535AA57.6010404-VXdhtT5mjnY@public.gmane.org>
2015-04-21 2:53 ` Dave Young
2015-04-24 8:01 ` Baoquan He
2015-04-24 8:25 ` Dave Young
2015-04-24 8:35 ` Baoquan He
2015-04-24 8:49 ` Dave Young
2015-04-28 8:54 ` Baoquan He
2015-04-28 9:00 ` Li, ZhenHua
[not found] ` <20150424084957.GC23912-0VdLhd/A9Pns0dwjj9W26R/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2015-05-04 16:23 ` Joerg Roedel
2015-05-05 6:14 ` Dave Young [this message]
[not found] ` <20150505061423.GC31063-0VdLhd/A9PlTxLCkMk2GaBcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2015-05-05 15:31 ` Joerg Roedel
[not found] ` <20150505153157.GQ15736-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-05-06 1:51 ` Dave Young
[not found] ` <20150506015135.GB14065-0VdLhd/A9PlTxLCkMk2GaBcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2015-05-06 2:37 ` Li, ZhenHua
2015-05-06 8:25 ` Joerg Roedel
2015-06-11 15:40 ` David Woodhouse
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=20150505061423.GC31063@dhcp-128-4.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bhe@redhat.com \
--cc=bhelgaas@google.com \
--cc=billsumnerlinux@gmail.com \
--cc=ddutile@redhat.com \
--cc=doug.hatch@hp.com \
--cc=dwmw2@infradead.org \
--cc=indou.takao@jp.fujitsu.com \
--cc=iommu@lists.linux-foundation.org \
--cc=ishii.hironobu@jp.fujitsu.com \
--cc=jerry.hoemann@hp.com \
--cc=joro@8bytes.org \
--cc=kexec@lists.infradead.org \
--cc=li.zhang6@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lisa.mitchell@hp.com \
--cc=rwright@hp.com \
--cc=tom.vaden@hp.com \
--cc=vgoyal@redhat.com \
--cc=zhen-hual@hp.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