From: Baoquan He <bhe@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: "Li, ZhenHua" <zhen-hual@hp.com>,
alex.williamson@redhat.com,
Takao Indoh <indou.takao@jp.fujitsu.com>,
tom.vaden@hp.com, dyoung@redhat.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, lisa.mitchell@hp.com,
jerry.hoemann@hp.com, iommu@lists.linux-foundation.org,
ddutile@redhat.com, doug.hatch@hp.com,
ishii.hironobu@jp.fujitsu.com, linux-pci@vger.kernel.org,
bhelgaas@google.com, li.zhang6@hp.com, dwmw2@infradead.org,
vgoyal@redhat.com
Subject: Re: [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO
Date: Mon, 15 Dec 2014 17:13:23 +0800 [thread overview]
Message-ID: <20141215091323.GA12150@dhcp-16-116.nay.redhat.com> (raw)
In-Reply-To: <20141212161102.GC24292@8bytes.org>
On 12/12/14 at 05:11pm, Joerg Roedel wrote:
> On Fri, Dec 12, 2014 at 10:25:31AM +0800, Li, ZhenHua wrote:
> > Sorry I have no plan yet.
> > Could you send me your logs on your AMD system?
>
> > On 12/10/2014 04:46 PM, Baoquan He wrote:
> > >This issue happens on AMD iommu too, do you have any plans or
> > >thoughts on that?
>
> I think the best approach for now is to get a prove-of-concept on the
> VT-d driver. If it works there the way we expect, we can implement the
> same handling in the AMD driver. But I see no reason to hold back the
> VT-d patches until it is also fixed for AMD systems.
Yes, I agree with you. Just raise this issue to upstream.
Thanks, Joerg.
next prev parent reply other threads:[~2014-12-15 9:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 8:04 [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO Li, Zhen-Hua
2014-10-21 8:04 ` [PATCH 1/5] iommu/vt-d: Update iommu_attach_domain() and its callers Li, Zhen-Hua
2014-10-21 8:04 ` [PATCH 2/5] iommu/vt-d: Items required for kdump Li, Zhen-Hua
2014-10-21 8:04 ` [PATCH 3/5] iommu/vt-d: data types and functions used " Li, Zhen-Hua
2014-10-21 8:04 ` [PATCH 4/5] iommu/vt-d: Add domain-id functions Li, Zhen-Hua
2014-10-21 8:04 ` [PATCH 5/5] iommu/vt-d: enable kdump support in iommu module Li, Zhen-Hua
2014-10-22 10:05 ` [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO Baoquan He
2014-10-22 10:22 ` Li, Zhen-Hua
2014-10-22 10:27 ` Baoquan He
2014-10-27 7:29 ` Li, ZhenHua
2014-10-27 10:44 ` Baoquan He
2014-11-06 1:31 ` Takao Indoh
2014-11-06 1:35 ` Li, ZhenHua
2014-11-06 1:48 ` Takao Indoh
2014-11-06 2:11 ` Li, ZhenHua
2014-11-06 7:51 ` Takao Indoh
2014-11-06 8:06 ` Li, ZhenHua
2014-11-14 6:27 ` Li, ZhenHua
2014-11-17 13:38 ` Joerg Roedel
2014-12-01 6:31 ` Li, ZhenHua
2014-12-01 12:33 ` Joerg Roedel
2014-12-10 8:46 ` Baoquan He
2014-12-12 2:25 ` Li, ZhenHua
2014-12-12 16:11 ` Joerg Roedel
2014-12-15 9:13 ` Baoquan He [this message]
2014-12-15 9:16 ` Baoquan He
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=20141215091323.GA12150@dhcp-16-116.nay.redhat.com \
--to=bhe@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=doug.hatch@hp.com \
--cc=dwmw2@infradead.org \
--cc=dyoung@redhat.com \
--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=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;
as well as URLs for NNTP newsgroup(s).