From: Joerg Roedel <joro@8bytes.org>
To: "Raj, Ashok" <ashok.raj@intel.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
David Woodhouse <dwmw2@infradead.org>,
Jacob Pan <jacob.jun.pan@intel.com>, CQ Tang <cq.tang@intel.com>,
Huang Ying <ying.huang@intel.com>,
Dave Hansen <dave.hansen@intel.com>
Subject: Re: [PATCH 0/4] Patches to support ring0 SVM and devtlb
Date: Fri, 18 Aug 2017 11:35:21 +0200 [thread overview]
Message-ID: <20170818093521.GM16908@8bytes.org> (raw)
In-Reply-To: <20170815145928.GA56170@otc-nc-03>
Hi Ashok,
On Tue, Aug 15, 2017 at 07:59:29AM -0700, Raj, Ashok wrote:
> I haven't received any update to this patchset..
>
> Could you help get this merged through your tree? we have tested this
> series internally.
The mm-notifier patch needs acks or rb from mm-developers before I can
merge this patch-set.
Regards,
Joerg
next prev parent reply other threads:[~2017-08-18 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 20:29 [PATCH 0/4] Patches to support ring0 SVM and devtlb Ashok Raj
[not found] ` <1502224170-5344-1-git-send-email-ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-08-08 20:29 ` [PATCH 1/4] iommu/vt-d: IOMMU Page Request needs to check if address is canonical Ashok Raj
2017-08-08 20:29 ` [PATCH 2/4] iommu/vt-d: Avoid calling virt_to_phys() on null pointer Ashok Raj
2017-08-08 20:29 ` [PATCH 3/4] mm: Add kernel MMU notifier to manage remote TLB Ashok Raj
2017-08-08 20:29 ` [PATCH 4/4] iommu/vt-d: Hooks to invalidate iotlb/devtlb when using supervisor PASID's Ashok Raj
2017-08-15 14:59 ` [PATCH 0/4] Patches to support ring0 SVM and devtlb Raj, Ashok
2017-08-15 15:49 ` David Woodhouse
2017-08-18 9:35 ` Joerg Roedel [this message]
[not found] ` <20170818093521.GM16908-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-08-21 17:20 ` Raj, Ashok
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=20170818093521.GM16908@8bytes.org \
--to=joro@8bytes.org \
--cc=ashok.raj@intel.com \
--cc=cq.tang@intel.com \
--cc=dave.hansen@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.huang@intel.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).