From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from 8bytes.org ([81.169.241.247] helo=theia.8bytes.org) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1XzSoO-0007dP-7Y for kexec@lists.infradead.org; Fri, 12 Dec 2014 16:11:25 +0000 Date: Fri, 12 Dec 2014 17:11:02 +0100 From: Joerg Roedel Subject: Re: [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO Message-ID: <20141212161102.GC24292@8bytes.org> References: <545ACF66.9050509@jp.fujitsu.com> <545AD061.4000102@hp.com> <545AD353.8060207@jp.fujitsu.com> <545AD8D3.90709@hp.com> <545B2885.8070009@jp.fujitsu.com> <545B2C07.1070701@hp.com> <5465A0E0.4020001@hp.com> <20141117133858.GA31920@8bytes.org> <20141210084652.GA25091@dhcp-16-105.nay.redhat.com> <548A521B.5020705@hp.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <548A521B.5020705@hp.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: "Li, ZhenHua" Cc: alex.williamson@redhat.com, Takao Indoh , Baoquan He , 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 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. Joerg _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO Date: Fri, 12 Dec 2014 17:11:02 +0100 Message-ID: <20141212161102.GC24292@8bytes.org> References: <545ACF66.9050509@jp.fujitsu.com> <545AD061.4000102@hp.com> <545AD353.8060207@jp.fujitsu.com> <545AD8D3.90709@hp.com> <545B2885.8070009@jp.fujitsu.com> <545B2C07.1070701@hp.com> <5465A0E0.4020001@hp.com> <20141117133858.GA31920@8bytes.org> <20141210084652.GA25091@dhcp-16-105.nay.redhat.com> <548A521B.5020705@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <548A521B.5020705-VXdhtT5mjnY@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: "Li, ZhenHua" Cc: Baoquan He , tom.vaden-VXdhtT5mjnY@public.gmane.org, dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, lisa.mitchell-VXdhtT5mjnY@public.gmane.org, iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, doug.hatch-VXdhtT5mjnY@public.gmane.org, ishii.hironobu-+CUm20s59erQFUHtdCDX3A@public.gmane.org, linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, li.zhang6-VXdhtT5mjnY@public.gmane.org, dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org, vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org List-Id: iommu@lists.linux-foundation.org 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. Joerg From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from 8bytes.org ([81.169.241.247]:38733 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753665AbaLLQLE (ORCPT ); Fri, 12 Dec 2014 11:11:04 -0500 Date: Fri, 12 Dec 2014 17:11:02 +0100 From: Joerg Roedel To: "Li, ZhenHua" Cc: Baoquan He , Takao Indoh , dwmw2@infradead.org, vgoyal@redhat.com, dyoung@redhat.com, iommu@lists.linux-foundation.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.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 Subject: Re: [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO Message-ID: <20141212161102.GC24292@8bytes.org> References: <545ACF66.9050509@jp.fujitsu.com> <545AD061.4000102@hp.com> <545AD353.8060207@jp.fujitsu.com> <545AD8D3.90709@hp.com> <545B2885.8070009@jp.fujitsu.com> <545B2C07.1070701@hp.com> <5465A0E0.4020001@hp.com> <20141117133858.GA31920@8bytes.org> <20141210084652.GA25091@dhcp-16-105.nay.redhat.com> <548A521B.5020705@hp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <548A521B.5020705@hp.com> Sender: linux-pci-owner@vger.kernel.org List-ID: 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. Joerg