From: Joerg Roedel <joro@8bytes.org>
To: "Li, ZhenHua" <zhen-hual@hp.com>
Cc: Takao Indoh <indou.takao@jp.fujitsu.com>,
bhe@redhat.com, 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
Date: Mon, 17 Nov 2014 14:38:59 +0100 [thread overview]
Message-ID: <20141117133858.GA31920@8bytes.org> (raw)
In-Reply-To: <5465A0E0.4020001@hp.com>
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
next prev parent reply other threads:[~2014-11-17 13:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 8:04 [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO Li, Zhen-Hua
2014-10-21 8:04 ` [PATCH 1/5] iommu/vt-d: Update iommu_attach_domain() and its callers Li, Zhen-Hua
2014-10-21 8:04 ` [PATCH 2/5] iommu/vt-d: Items required for kdump Li, Zhen-Hua
2014-10-21 8:04 ` [PATCH 3/5] iommu/vt-d: data types and functions used " Li, Zhen-Hua
2014-10-21 8:04 ` [PATCH 4/5] iommu/vt-d: Add domain-id functions Li, Zhen-Hua
2014-10-21 8:04 ` [PATCH 5/5] iommu/vt-d: enable kdump support in iommu module Li, Zhen-Hua
2014-10-22 10:05 ` [PATCH 0/5] iommu/vt-d: Fix crash dump failure caused by legacy DMA/IO Baoquan He
2014-10-22 10:22 ` Li, Zhen-Hua
2014-10-22 10:27 ` Baoquan He
2014-10-27 7:29 ` Li, ZhenHua
2014-10-27 10:44 ` Baoquan He
2014-11-06 1:31 ` Takao Indoh
2014-11-06 1:35 ` Li, ZhenHua
2014-11-06 1:48 ` Takao Indoh
2014-11-06 2:11 ` Li, ZhenHua
2014-11-06 7:51 ` Takao Indoh
2014-11-06 8:06 ` Li, ZhenHua
2014-11-14 6:27 ` Li, ZhenHua
2014-11-17 13:38 ` Joerg Roedel [this message]
2014-12-01 6:31 ` Li, ZhenHua
2014-12-01 12:33 ` Joerg Roedel
2014-12-10 8:46 ` Baoquan He
2014-12-12 2:25 ` Li, ZhenHua
2014-12-12 16:11 ` Joerg Roedel
2014-12-15 9:13 ` Baoquan He
2014-12-15 9:16 ` Baoquan He
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=20141117133858.GA31920@8bytes.org \
--to=joro@8bytes.org \
--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=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=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=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;
as well as URLs for NNTP newsgroup(s).