From: Peter Xu <peterx@redhat.com>
To: Liu Yi L <yi.l.liu@intel.com>
Cc: kevin.tian@intel.com, mst@redhat.com, jun.j.tian@intel.com,
qemu-devel@nongnu.org, pbonzini@redhat.com, yi.y.sun@intel.co
Subject: Re: [PATCH v1 0/2] intel_iommu: two fixes to intel scalable vIOMMU
Date: Fri, 3 Jan 2020 10:28:14 -0500 [thread overview]
Message-ID: <20200103152814.GA157597@xz-x1> (raw)
In-Reply-To: <1578058086-4288-1-git-send-email-yi.l.liu@intel.com>
On Fri, Jan 03, 2020 at 09:28:04PM +0800, Liu Yi L wrote:
> These two fixes are found in vSVA implementation, and could be
> upstreamed separately. Please feel free give your comments.
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
prev parent reply other threads:[~2020-01-03 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 13:28 [PATCH v1 0/2] intel_iommu: two fixes to intel scalable vIOMMU Liu Yi L
2020-01-03 13:28 ` [PATCH v1 1/2] intel_iommu: a fix to vtd_find_as_from_bus_num() Liu Yi L
2020-01-03 13:28 ` [PATCH v1 2/2] intel_iommu: add present bit check for pasid table entries Liu Yi L
2020-01-03 15:28 ` Peter Xu [this message]
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=20200103152814.GA157597@xz-x1 \
--to=peterx@redhat.com \
--cc=jun.j.tian@intel.com \
--cc=kevin.tian@intel.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@intel.co \
/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).