[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141215091323.GA12150@dhcp-16-116.nay.redhat.com>
Date: Mon, 15 Dec 2014 17:13:23 +0800
From: Baoquan He <bhe@...hat.com>
To: Joerg Roedel <joro@...tes.org>
Cc: "Li, ZhenHua" <zhen-hual@...com>, alex.williamson@...hat.com,
Takao Indoh <indou.takao@...fujitsu.com>, tom.vaden@...com,
dyoung@...hat.com, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, lisa.mitchell@...com,
jerry.hoemann@...com, iommu@...ts.linux-foundation.org,
ddutile@...hat.com, doug.hatch@...com,
ishii.hironobu@...fujitsu.com, linux-pci@...r.kernel.org,
bhelgaas@...gle.com, li.zhang6@...com, dwmw2@...radead.org,
vgoyal@...hat.com
Subject: Re: [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy
DMA/IO
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists