From: Joerg Roedel <joro@8bytes.org>
To: Baoquan He <bhe@redhat.com>
Cc: xlpang@redhat.com, Don Brace <don.brace@microsemi.com>,
Myron Stowe <myron.stowe@redhat.com>,
kexec@lists.infradead.org, LKML <linux-kernel@vger.kernel.org>,
iommu@lists.linux-foundation.org,
Myron Stowe <myron.stowe@gmail.com>,
Dave Young <dyoung@redhat.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] iommu/vt-d: Flush old iotlb for kdump when the device gets context mapped
Date: Wed, 30 Nov 2016 15:26:43 +0100 [thread overview]
Message-ID: <20161130142642.GJ2078@8bytes.org> (raw)
In-Reply-To: <20161130102334.GC4192@x1>
On Wed, Nov 30, 2016 at 06:23:34PM +0800, Baoquan He wrote:
> OK, talked with Xunlei. The old cache could be entry with present bit
> set.
-EPARSE
Anyway, what I was trying to say is, that the IOMMU TLB is tagged with
domain-ids, and that there is also a context-cache which maps device-ids
to domain-ids.
If we update the context entry then we need to flush only the context
entry, as it will point to a new domain-id then and future IOTLB lookups
in the IOMMU will be using the new domain-id and do not match the old
entries.
Joerg
next prev parent reply other threads:[~2016-11-30 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 9:02 [PATCH] iommu/vt-d: Flush old iotlb for kdump when the device gets context mapped Xunlei Pang
2016-11-16 9:13 ` Xunlei Pang
2016-11-16 14:58 ` Myron Stowe
2016-11-17 2:47 ` Xunlei Pang
2016-11-29 14:35 ` Joerg Roedel
2016-11-30 8:15 ` Xunlei Pang
2016-11-30 9:03 ` Baoquan He
2016-11-30 9:53 ` Baoquan He
2016-11-30 10:23 ` Baoquan He
2016-11-30 14:26 ` Joerg Roedel [this message]
2016-12-01 2:15 ` Xunlei Pang
2016-12-01 10:33 ` Joerg Roedel
2016-12-01 11:44 ` Xunlei Pang
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=20161130142642.GJ2078@8bytes.org \
--to=joro@8bytes.org \
--cc=bhe@redhat.com \
--cc=don.brace@microsemi.com \
--cc=dwmw2@infradead.org \
--cc=dyoung@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myron.stowe@gmail.com \
--cc=myron.stowe@redhat.com \
--cc=xlpang@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 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).