From: Joerg Roedel <joro@8bytes.org>
To: Xunlei Pang <xlpang@redhat.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Myron Stowe <myron.stowe@gmail.com>,
Joseph Szczypek <jszczype@redhat.com>,
Don Brace <don.brace@microsemi.com>, Baoquan He <bhe@redhat.com>,
Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH v3] iommu/vt-d: Flush old iommu caches for kdump when the device gets context mapped
Date: Wed, 4 Jan 2017 15:14:49 +0100 [thread overview]
Message-ID: <20170104141449.GA10632@8bytes.org> (raw)
In-Reply-To: <1480939747-31916-1-git-send-email-xlpang@redhat.com>
On Mon, Dec 05, 2016 at 08:09:07PM +0800, Xunlei Pang wrote:
> v2->v3:
> Flush context cache only and add Fixes-tag, according to Joerg's comments.
>
> drivers/iommu/intel-iommu.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
Applied to the fixes branch, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Xunlei Pang <xlpang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Don Brace <don.brace-dzo6w/eZyo2tG0bUXCXiUA@public.gmane.org>,
Joseph Szczypek
<jszczype-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: [PATCH v3] iommu/vt-d: Flush old iommu caches for kdump when the device gets context mapped
Date: Wed, 4 Jan 2017 15:14:49 +0100 [thread overview]
Message-ID: <20170104141449.GA10632@8bytes.org> (raw)
In-Reply-To: <1480939747-31916-1-git-send-email-xlpang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Mon, Dec 05, 2016 at 08:09:07PM +0800, Xunlei Pang wrote:
> v2->v3:
> Flush context cache only and add Fixes-tag, according to Joerg's comments.
>
> drivers/iommu/intel-iommu.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
Applied to the fixes branch, thanks.
next prev parent reply other threads:[~2017-01-04 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 12:09 [PATCH v3] iommu/vt-d: Flush old iommu caches for kdump when the device gets context mapped Xunlei Pang
2016-12-05 12:09 ` Xunlei Pang
2016-12-06 16:03 ` Joerg Roedel
2017-01-03 15:23 ` Myron Stowe
2017-01-03 15:23 ` Myron Stowe
2017-01-03 16:11 ` Joerg Roedel
2017-01-03 16:11 ` Joerg Roedel
2016-12-06 22:03 ` Don Brace
2016-12-06 22:03 ` Don Brace
2017-01-04 14:14 ` Joerg Roedel [this message]
2017-01-04 14:14 ` Joerg Roedel
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=20170104141449.GA10632@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=jszczype@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myron.stowe@gmail.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 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.