From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from g4t3425.houston.hp.com ([15.201.208.53]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1XzFwT-0006Ga-9H for kexec@lists.infradead.org; Fri, 12 Dec 2014 02:26:53 +0000 Message-ID: <548A521B.5020705@hp.com> Date: Fri, 12 Dec 2014 10:25:31 +0800 From: "Li, ZhenHua" MIME-Version: 1.0 Subject: Re: [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO References: <1413878659-1383-1-git-send-email-zhen-hual@hp.com> <20141022100525.GD9060@dhcp-16-116.nay.redhat.com> <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> In-Reply-To: <20141210084652.GA25091@dhcp-16-105.nay.redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Baoquan He Cc: alex.williamson@redhat.com, Takao Indoh , tom.vaden@hp.com, dyoung@redhat.com, Joerg Roedel , 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 Sorry I have no plan yet. Could you send me your logs on your AMD system? Thanks Zhenhua On 12/10/2014 04:46 PM, Baoquan He wrote: > Hi Joerg, ZhenHua, > > This issue happens on AMD iommu too, do you have any plans or > thoughts on that? > > Thanks > Baoquan > > On 11/17/14 at 02:38pm, Joerg Roedel wrote: >> On Fri, Nov 14, 2014 at 02:27:44PM +0800, Li, ZhenHua wrote: >>> I am working following your directions: >>> >>> 1. If the VT-d driver finds the IOMMU enabled, it reuses its root entry >>> table, and do NOT disable-enable iommu. Other data will be copied. >>> >>> 2. When a device driver issues the first dma_map command for a >>> device, we assign a new and empty page-table, thus removing all >>> mappings from the old kernel for the device. >>> >>> Please let me know if I get something wrong. >> >> Yes, this sounds right. Happily waiting for patches :) >> >> >> 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: "Li, ZhenHua" Subject: Re: [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO Date: Fri, 12 Dec 2014 10:25:31 +0800 Message-ID: <548A521B.5020705@hp.com> References: <1413878659-1383-1-git-send-email-zhen-hual@hp.com> <20141022100525.GD9060@dhcp-16-116.nay.redhat.com> <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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20141210084652.GA25091-je1gSBvt1TeLcxizHhUEZR/sF2h8X+2i0E9HWUfgJXw@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: Baoquan He Cc: 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 Sorry I have no plan yet. Could you send me your logs on your AMD system? Thanks Zhenhua On 12/10/2014 04:46 PM, Baoquan He wrote: > Hi Joerg, ZhenHua, > > This issue happens on AMD iommu too, do you have any plans or > thoughts on that? > > Thanks > Baoquan > > On 11/17/14 at 02:38pm, Joerg Roedel wrote: >> On Fri, Nov 14, 2014 at 02:27:44PM +0800, Li, ZhenHua wrote: >>> I am working following your directions: >>> >>> 1. If the VT-d driver finds the IOMMU enabled, it reuses its root entry >>> table, and do NOT disable-enable iommu. Other data will be copied. >>> >>> 2. When a device driver issues the first dma_map command for a >>> device, we assign a new and empty page-table, thus removing all >>> mappings from the old kernel for the device. >>> >>> Please let me know if I get something wrong. >> >> Yes, this sounds right. Happily waiting for patches :) >> >> >> Joerg >> From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g4t3425.houston.hp.com ([15.201.208.53]:53103 "EHLO g4t3425.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750859AbaLLC00 (ORCPT ); Thu, 11 Dec 2014 21:26:26 -0500 Message-ID: <548A521B.5020705@hp.com> Date: Fri, 12 Dec 2014 10:25:31 +0800 From: "Li, ZhenHua" MIME-Version: 1.0 To: Baoquan He CC: Joerg Roedel , 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 References: <1413878659-1383-1-git-send-email-zhen-hual@hp.com> <20141022100525.GD9060@dhcp-16-116.nay.redhat.com> <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> In-Reply-To: <20141210084652.GA25091@dhcp-16-105.nay.redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-pci-owner@vger.kernel.org List-ID: Sorry I have no plan yet. Could you send me your logs on your AMD system? Thanks Zhenhua On 12/10/2014 04:46 PM, Baoquan He wrote: > Hi Joerg, ZhenHua, > > This issue happens on AMD iommu too, do you have any plans or > thoughts on that? > > Thanks > Baoquan > > On 11/17/14 at 02:38pm, Joerg Roedel wrote: >> On Fri, Nov 14, 2014 at 02:27:44PM +0800, Li, ZhenHua wrote: >>> I am working following your directions: >>> >>> 1. If the VT-d driver finds the IOMMU enabled, it reuses its root entry >>> table, and do NOT disable-enable iommu. Other data will be copied. >>> >>> 2. When a device driver issues the first dma_map command for a >>> device, we assign a new and empty page-table, thus removing all >>> mappings from the old kernel for the device. >>> >>> Please let me know if I get something wrong. >> >> Yes, this sounds right. Happily waiting for patches :) >> >> >> Joerg >>