From: Anthony PERARD <anthony.perard@citrix.com>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: qemu-devel@nongnu.org, xen-devel@lists.xenproject.org,
Chao Gao <chao.gao@intel.com>,
sstabellini@kernel.org, mst@redhat.com, pbonzini@redhat.com,
rth@twiddle.net, ehabkost@redhat.com, marcel@redhat.com,
kevin.tian@intel.com
Subject: Re: [Qemu-devel] [PATCH V2 2/3] xen-pt: bind/unbind interrupt remapping format MSI
Date: Fri, 11 Aug 2017 19:04:38 +0100 [thread overview]
Message-ID: <20170811180438.GI1519@perard.uk.xensource.com> (raw)
In-Reply-To: <1502311882-11038-3-git-send-email-tianyu.lan@intel.com>
On Wed, Aug 09, 2017 at 04:51:21PM -0400, Lan Tianyu wrote:
> From: Chao Gao <chao.gao@intel.com>
>
> If a vIOMMU is exposed to guest, guest will configure the msi to remapping
> format. The original code isn't suitable to the new format. A new pair
> bind/unbind interfaces are added for this usage. This patch recognizes
> this case and uses new interfaces to bind/unbind msi.
>
> Signed-off-by: Chao Gao <chao.gao@intel.com>
> Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>
That patch series can be applied once the Xen side patches are merged.
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2017-08-11 18:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 20:51 [Qemu-devel] [PATCH v2 0/3] Qemu: Add Xen vIOMMU interrupt remapping function support Lan Tianyu
2017-08-09 20:51 ` [Qemu-devel] [PATCH V2 1/3] i386/msi: Correct mask of destination ID in MSI address Lan Tianyu
2017-08-09 20:51 ` [Qemu-devel] [PATCH V2 2/3] xen-pt: bind/unbind interrupt remapping format MSI Lan Tianyu
2017-08-11 18:04 ` Anthony PERARD [this message]
2017-08-15 3:10 ` Lan Tianyu
2017-08-21 20:29 ` Stefano Stabellini
2017-08-09 20:51 ` [Qemu-devel] [PATCH V2 3/3] msi: Handle remappable format interrupt request Lan Tianyu
2017-08-10 9:04 ` [Qemu-devel] [PATCH v2 0/3] Qemu: Add Xen vIOMMU interrupt remapping function support Paolo Bonzini
2017-08-10 9:38 ` Lan Tianyu
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=20170811180438.GI1519@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=chao.gao@intel.com \
--cc=ehabkost@redhat.com \
--cc=kevin.tian@intel.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sstabellini@kernel.org \
--cc=tianyu.lan@intel.com \
--cc=xen-devel@lists.xenproject.org \
/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).