From: "Li, ZhenHua" <zhen-hual@hp.com>
To: Dave Young <dyoung@redhat.com>
Cc: Joerg Roedel <joro@8bytes.org>, Baoquan He <bhe@redhat.com>,
dwmw2@infradead.org, indou.takao@jp.fujitsu.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, "Li,
ZhenHua" <zhen-hual@hp.com>
Subject: Re: [PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel
Date: Wed, 06 May 2015 10:37:01 +0800 [thread overview]
Message-ID: <55497E4D.6020202@hp.com> (raw)
In-Reply-To: <20150506015135.GB14065@dhcp-128-4.nay.redhat.com>
Dave,
This patchset will only write root tables in old kernel, if it is
corrupted, faults will also happen in old kernel, and hardware would
mark it. So things will not go worse..
Thanks
Zhenhua
On 05/06/2015 09:51 AM, Dave Young wrote:
> On 05/05/15 at 05:31pm, Joerg Roedel wrote:
>> On Tue, May 05, 2015 at 02:14:23PM +0800, Dave Young wrote:
>>> The failure is nothing different, but as I said in another reply the
>>> difference is we could use corrupted data to possiblly cause more failure.
>>
>> I still fail to see how things can get more worse than they already are
>> by reusing the old data (we just reuse it, we do not modify anything
>
> DMA write will modify system ram, if the old data is corrupted it is possible
> that DMA operation modify wrong ram regions because of wrong mapping.
> Am I missing something and is it not possible?
>
> Thanks
> Dave
>
WARNING: multiple messages have this Message-ID (diff)
From: "Li, ZhenHua" <zhen-hual-VXdhtT5mjnY@public.gmane.org>
To: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
tom.vaden-VXdhtT5mjnY@public.gmane.org,
rwright-VXdhtT5mjnY@public.gmane.org,
linux-pci-u79uwXL29TY76Z2rM5mHXA@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,
"Li, ZhenHua" <zhen-hual-VXdhtT5mjnY@public.gmane.org>,
doug.hatch-VXdhtT5mjnY@public.gmane.org,
ishii.hironobu-+CUm20s59erQFUHtdCDX3A@public.gmane.org,
bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
billsumnerlinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
li.zhang6-VXdhtT5mjnY@public.gmane.org,
dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel
Date: Wed, 06 May 2015 10:37:01 +0800 [thread overview]
Message-ID: <55497E4D.6020202@hp.com> (raw)
In-Reply-To: <20150506015135.GB14065-0VdLhd/A9PlTxLCkMk2GaBcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
Dave,
This patchset will only write root tables in old kernel, if it is
corrupted, faults will also happen in old kernel, and hardware would
mark it. So things will not go worse..
Thanks
Zhenhua
On 05/06/2015 09:51 AM, Dave Young wrote:
> On 05/05/15 at 05:31pm, Joerg Roedel wrote:
>> On Tue, May 05, 2015 at 02:14:23PM +0800, Dave Young wrote:
>>> The failure is nothing different, but as I said in another reply the
>>> difference is we could use corrupted data to possiblly cause more failure.
>>
>> I still fail to see how things can get more worse than they already are
>> by reusing the old data (we just reuse it, we do not modify anything
>
> DMA write will modify system ram, if the old data is corrupted it is possible
> that DMA operation modify wrong ram regions because of wrong mapping.
> Am I missing something and is it not possible?
>
> Thanks
> Dave
>
WARNING: multiple messages have this Message-ID (diff)
From: "Li, ZhenHua" <zhen-hual@hp.com>
To: Dave Young <dyoung@redhat.com>
Cc: alex.williamson@redhat.com, indou.takao@jp.fujitsu.com,
Baoquan He <bhe@redhat.com>,
tom.vaden@hp.com, rwright@hp.com, linux-pci@vger.kernel.org,
Joerg Roedel <joro@8bytes.org>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
lisa.mitchell@hp.com, jerry.hoemann@hp.com,
iommu@lists.linux-foundation.org, "Li,
ZhenHua" <zhen-hual@hp.com>,
ddutile@redhat.com, doug.hatch@hp.com,
ishii.hironobu@jp.fujitsu.com, bhelgaas@google.com,
billsumnerlinux@gmail.com, li.zhang6@hp.com, dwmw2@infradead.org,
vgoyal@redhat.com
Subject: Re: [PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel
Date: Wed, 06 May 2015 10:37:01 +0800 [thread overview]
Message-ID: <55497E4D.6020202@hp.com> (raw)
In-Reply-To: <20150506015135.GB14065@dhcp-128-4.nay.redhat.com>
Dave,
This patchset will only write root tables in old kernel, if it is
corrupted, faults will also happen in old kernel, and hardware would
mark it. So things will not go worse..
Thanks
Zhenhua
On 05/06/2015 09:51 AM, Dave Young wrote:
> On 05/05/15 at 05:31pm, Joerg Roedel wrote:
>> On Tue, May 05, 2015 at 02:14:23PM +0800, Dave Young wrote:
>>> The failure is nothing different, but as I said in another reply the
>>> difference is we could use corrupted data to possiblly cause more failure.
>>
>> I still fail to see how things can get more worse than they already are
>> by reusing the old data (we just reuse it, we do not modify anything
>
> DMA write will modify system ram, if the old data is corrupted it is possible
> that DMA operation modify wrong ram regions because of wrong mapping.
> Am I missing something and is it not possible?
>
> Thanks
> Dave
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-05-06 2:38 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 8:42 [PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 01/10] iommu/vt-d: New function to attach domain with id Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 02/10] iommu/vt-d: Items required for kdump Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 03/10] iommu/vt-d: Function to get old context entry Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 04/10] iommu/vt-d: functions to copy data from old mem Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-05-07 7:49 ` Baoquan He
2015-05-07 7:49 ` Baoquan He
2015-05-07 8:33 ` Li, ZhenHua
2015-05-07 8:33 ` Li, ZhenHua
2015-05-07 8:33 ` Li, ZhenHua
2015-04-10 8:42 ` [PATCH v10 05/10] iommu/vt-d: Add functions to load and save old re Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 06/10] iommu/vt-d: datatypes and functions used for kdump Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 07/10] iommu/vt-d: enable kdump support in iommu module Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 08/10] iommu/vt-d: assign new page table for dma_map Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 09/10] iommu/vt-d: Copy functions for irte Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` [PATCH v10 10/10] iommu/vt-d: Use old irte in kdump kernel Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-10 8:42 ` Li, Zhen-Hua
2015-04-15 0:57 ` [PATCH v10 0/10] iommu/vt-d: Fix intel vt-d faults " Dave Young
2015-04-15 5:47 ` Li, ZhenHua
2015-04-15 5:47 ` Li, ZhenHua
2015-04-15 5:47 ` Li, ZhenHua
2015-04-15 6:48 ` Dave Young
2015-04-15 6:48 ` Dave Young
2015-04-21 1:39 ` Li, ZhenHua
2015-04-21 1:39 ` Li, ZhenHua
2015-04-21 2:53 ` Dave Young
2015-04-21 2:53 ` Dave Young
2015-04-21 2:53 ` Dave Young
2015-04-24 8:01 ` Baoquan He
2015-04-24 8:01 ` Baoquan He
2015-04-24 8:25 ` Dave Young
2015-04-24 8:25 ` Dave Young
2015-04-24 8:35 ` Baoquan He
2015-04-24 8:35 ` Baoquan He
2015-04-24 8:49 ` Dave Young
2015-04-24 8:49 ` Dave Young
2015-04-28 8:54 ` Baoquan He
2015-04-28 8:54 ` Baoquan He
2015-04-28 9:00 ` Li, ZhenHua
2015-04-28 9:00 ` Li, ZhenHua
2015-05-04 16:23 ` Joerg Roedel
2015-05-04 16:23 ` Joerg Roedel
2015-05-05 6:14 ` Dave Young
2015-05-05 6:14 ` Dave Young
2015-05-05 15:31 ` Joerg Roedel
2015-05-05 15:31 ` Joerg Roedel
2015-05-06 1:51 ` Dave Young
2015-05-06 1:51 ` Dave Young
2015-05-06 1:51 ` Dave Young
2015-05-06 2:37 ` Li, ZhenHua [this message]
2015-05-06 2:37 ` Li, ZhenHua
2015-05-06 2:37 ` Li, ZhenHua
2015-05-06 8:25 ` Joerg Roedel
2015-05-06 8:25 ` Joerg Roedel
2015-04-23 8:35 ` Li, ZhenHua
2015-04-23 8:35 ` Li, ZhenHua
2015-04-23 8:35 ` Li, ZhenHua
2015-04-23 8:38 ` Li, ZhenHua
2015-04-23 8:38 ` Li, ZhenHua
2015-04-23 8:38 ` Li, ZhenHua
2015-04-29 11:20 ` Baoquan He
2015-04-29 11:20 ` Baoquan He
2015-04-29 11:20 ` Baoquan He
2015-05-03 8:55 ` Baoquan He
2015-05-03 8:55 ` Baoquan He
2015-05-03 8:55 ` Baoquan He
2015-05-04 3:06 ` Li, ZhenHua
2015-05-04 3:06 ` Li, ZhenHua
2015-05-04 3:06 ` Li, ZhenHua
2015-05-04 3:17 ` Baoquan He
2015-05-04 3:17 ` Baoquan He
2015-05-07 17:32 ` Joerg Roedel
2015-05-07 17:32 ` Joerg Roedel
2015-05-08 1:00 ` Li, ZhenHua
2015-05-08 1:00 ` Li, ZhenHua
2015-05-08 1:00 ` Li, ZhenHua
2015-06-11 15:40 ` David Woodhouse
2015-06-11 15:40 ` David Woodhouse
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=55497E4D.6020202@hp.com \
--to=zhen-hual@hp.com \
--cc=alex.williamson@redhat.com \
--cc=bhe@redhat.com \
--cc=bhelgaas@google.com \
--cc=billsumnerlinux@gmail.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=rwright@hp.com \
--cc=tom.vaden@hp.com \
--cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.