From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 5 May 2015 17:23:43 +0200 From: Joerg Roedel To: Dave Young Cc: "Li, Zhen-Hua" , dwmw2@infradead.org, indou.takao@jp.fujitsu.com, bhe@redhat.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 v9 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel Message-ID: <20150505152343.GP15736@8bytes.org> References: <1426743388-26908-1-git-send-email-zhen-hual@hp.com> <20150403084031.GF22579@dhcp-128-53.nay.redhat.com> <20150504110551.GD15736@8bytes.org> <20150505060931.GB31063@dhcp-128-4.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20150505060931.GB31063@dhcp-128-4.nay.redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: On Tue, May 05, 2015 at 02:09:31PM +0800, Dave Young wrote: > I agree that we can do nothing with the old corrupted data, but I worry > about the future corruption after using the old corrupted data. I wonder > if we can mark all the oldmem as readonly so that we can lower the risk. > Is it resonable? Do you mean marking it read-only for the devices? That will very likely cause DMAR faults, re-introducing the problem this patch-set tries to fix. Joerg