From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 0/3] x86/vMSI-X: further write snoop improvements
Date: Thu, 28 Apr 2016 11:26:44 +0100 [thread overview]
Message-ID: <20160428102644.GA20763@citrix.com> (raw)
In-Reply-To: <5721F94C02000078000E6B1E@prv-mh.provo.novell.com>
On Thu, Apr 28, 2016 at 03:51:40AM -0600, Jan Beulich wrote:
> >>> On 28.04.16 at 11:35, <JBeulich@suse.com> wrote:
> > 1: add further checks to snoop logic
> > 2: also snoop qword writes
> > 3: also snoop REP MOVS
> >
> > Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> Wei,
>
> I've only now realized that I should have Cc-ed you on this series (all
> intended for 4.7).
>
Subject to ack / review from Andrew / Paul:
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-28 10:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 9:35 [PATCH 0/3] x86/vMSI-X: further write snoop improvements Jan Beulich
2016-04-28 9:49 ` [PATCH 1/3] x86/vMSI-X: add further checks to snoop logic Jan Beulich
2016-04-28 10:22 ` Andrew Cooper
2016-04-28 10:44 ` Paul Durrant
2016-04-28 9:49 ` [PATCH 2/3] x86/vMSI-X: also snoop qword writes Jan Beulich
2016-04-28 10:27 ` Andrew Cooper
2016-04-28 10:52 ` Paul Durrant
2016-04-28 9:50 ` [PATCH 3/3] x86/vMSI-X: also snoop REP MOVS Jan Beulich
2016-04-28 10:34 ` Andrew Cooper
2016-04-28 10:44 ` Jan Beulich
2016-04-28 11:17 ` Paul Durrant
2016-04-28 11:44 ` Jan Beulich
2016-04-28 11:58 ` Paul Durrant
2016-04-28 12:30 ` Jan Beulich
2016-04-28 12:44 ` Paul Durrant
2016-04-28 9:51 ` [PATCH 0/3] x86/vMSI-X: further write snoop improvements Jan Beulich
2016-04-28 10:26 ` Wei Liu [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=20160428102644.GA20763@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=paul.durrant@citrix.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 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.