From: Dave Young <dyoung@redhat.com>
To: "Li, Zhen-Hua" <zhen-hual@hp.com>
Cc: "dwmw2@infradead.org" <dwmw2@infradead.org>,
"indou.takao@jp.fujitsu.com" <indou.takao@jp.fujitsu.com>,
"bhe@redhat.com" <bhe@redhat.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"vgoyal@redhat.com" <vgoyal@redhat.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"ddutile@redhat.com" <ddutile@redhat.com>,
"ishii.hironobu@jp.fujitsu.com" <ishii.hironobu@jp.fujitsu.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"Hatch, Douglas B (HPS Linux PM)" <doug.hatch@hp.com>,
"Hoemann, Jerry" <jerry.hoemann@hp.com>,
"Vaden, Tom (HP Server OS Architecture)" <tom.vaden@hp.com>,
"Zhang, Li (Zoe@HPservers-Core-OE-PSC)" <li.zh>
Subject: Re: [PATCH v9 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel
Date: Tue, 7 Apr 2015 11:49:57 +0800 [thread overview]
Message-ID: <20150407034957.GC7213@localhost.localdomain> (raw)
In-Reply-To: <534F7596-2172-4BE1-B374-4D18D2DA5110@hp.com>
On 04/03/15 at 02:05pm, Li, Zhen-Hua wrote:
> The hardware will do some verification, but not completely. If people think the OS should also do this, then it should be another patchset, I think.
If there is chance to corrupt more memory I think it is not a right way.
We should think about a better solution instead of fix it later.
Thanks
Dave
next prev parent reply other threads:[~2015-04-07 3:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 5:36 [PATCH v9 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel Li, Zhen-Hua
[not found] ` <1426743388-26908-1-git-send-email-zhen-hual-VXdhtT5mjnY@public.gmane.org>
2015-03-19 5:36 ` [PATCH v9 01/10] iommu/vt-d: New function to attach domain with id Li, Zhen-Hua
2015-03-19 5:36 ` [PATCH v9 02/10] iommu/vt-d: Items required for kdump Li, Zhen-Hua
2015-03-19 5:36 ` [PATCH v9 03/10] iommu/vt-d: Function to get old context entry Li, Zhen-Hua
2015-03-19 5:36 ` [PATCH v9 04/10] iommu/vt-d: functions to copy data from old mem Li, Zhen-Hua
2015-03-19 5:36 ` [PATCH v9 05/10] iommu/vt-d: Add functions to load and save old re Li, Zhen-Hua
2015-03-19 5:36 ` [PATCH v9 06/10] iommu/vt-d: datatypes and functions used for kdump Li, Zhen-Hua
2015-03-19 5:36 ` [PATCH v9 07/10] iommu/vt-d: enable kdump support in iommu module Li, Zhen-Hua
2015-04-02 11:06 ` Joerg Roedel
[not found] ` <20150402110608.GL4441-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-04-03 7:45 ` Li, ZhenHua
2015-03-19 5:36 ` [PATCH v9 08/10] iommu/vt-d: assign new page table for dma_map Li, Zhen-Hua
2015-03-19 5:36 ` [PATCH v9 09/10] iommu/vt-d: Copy functions for irte Li, Zhen-Hua
2015-03-19 5:36 ` [PATCH v9 10/10] iommu/vt-d: Use old irte in kdump kernel Li, Zhen-Hua
2015-04-02 11:11 ` [PATCH v9 0/10] iommu/vt-d: Fix intel vt-d faults " Joerg Roedel
[not found] ` <20150402111133.GM4441-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-04-03 7:54 ` Li, ZhenHua
2015-04-03 8:28 ` Dave Young
[not found] ` <20150403082816.GE22579-0VdLhd/A9PldIt/LePPtNh/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2015-04-03 8:31 ` Li, ZhenHua
2015-04-03 8:40 ` Dave Young
[not found] ` <20150403084031.GF22579-0VdLhd/A9PldIt/LePPtNh/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2015-04-03 9:01 ` Li, ZhenHua
2015-04-03 9:21 ` Dave Young
2015-04-03 14:05 ` Li, Zhen-Hua
2015-04-07 3:49 ` Dave Young [this message]
[not found] ` <20150403092111.GG22579-0VdLhd/A9PldIt/LePPtNh/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2015-04-05 1:54 ` Baoquan He
2015-04-07 3:46 ` Dave Young
2015-04-07 9:08 ` Dave Young
2015-04-07 9:55 ` Li, ZhenHua
[not found] ` <5523A977.1030707-VXdhtT5mjnY@public.gmane.org>
2015-04-08 3:33 ` Dave Young
[not found] ` <20150407034622.GB7213-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-04-07 14:12 ` Don Dutile
2015-05-07 14:00 ` Dave Young
[not found] ` <20150507140029.GC4559-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-05-07 14:25 ` Don Dutile
2015-05-08 1:21 ` Dave Young
[not found] ` <20150508012118.GA4809-0VdLhd/A9PlTxLCkMk2GaBcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2015-05-10 21:37 ` Don Dutile
2015-05-10 21:31 ` Don Dutile
2015-05-04 11:05 ` Joerg Roedel
2015-05-04 15:21 ` Don Dutile
2015-05-05 6:09 ` Dave Young
[not found] ` <20150505060931.GB31063-0VdLhd/A9PlTxLCkMk2GaBcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2015-05-05 15:23 ` Joerg Roedel
2015-05-06 1:46 ` Dave Young
[not found] ` <20150506014649.GA14065-0VdLhd/A9PlTxLCkMk2GaBcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2015-05-06 8:16 ` Joerg Roedel
[not found] ` <20150506081617.GB20611-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-05-07 13:25 ` Dave Young
2015-05-07 13:56 ` Dave Young
2015-05-11 10:11 ` Joerg Roedel
2015-05-12 5:57 ` Dave Young
2015-05-12 6:41 ` Dave Young
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=20150407034957.GC7213@localhost.localdomain \
--to=dyoung@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bhe@redhat.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=doug.hatch@hp.com \
--cc=dwmw2@infradead.org \
--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=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tom.vaden@hp.com \
--cc=vgoyal@redhat.com \
--cc=zhen-hual@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox