From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: x86 patch ping
Date: Fri, 8 Apr 2016 13:18:22 +0100 [thread overview]
Message-ID: <5707A18E.3030707@citrix.com> (raw)
In-Reply-To: <5707ADA902000078000E60AA@prv-mh.provo.novell.com>
On 08/04/16 13:10, Jan Beulich wrote:
> Andrew,
>
> could I please get acks or otherwise on
>
> http://lists.xen.org/archives/html/xen-devel/2016-03/msg01469.html
>
> http://lists.xen.org/archives/html/xen-devel/2016-03/msg02167.html
> (with the 1st patch having gone in already)
>
> http://lists.xen.org/archives/html/xen-devel/2016-04/msg00040.html
>
> There are also
> http://lists.xen.org/archives/html/xen-devel/2016-03/msg03746.html
> http://lists.xen.org/archives/html/xen-devel/2016-03/msg03747.html
> but I guess I'll put them in without further acks, considering they
> are simply ports from Linux.
These last 3 links ("x86/vMSI-X: fix qword write" and the two from
linux) are straightforward.
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
The first I will need to do a closer review of.
The SMEP/SMAP series is still very concerning. I need to follow up on
the performance testing, but it currently looks like no real improvement
on the 40-70% performance hit for 32bit PV guests.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-08 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 12:10 x86 patch ping Jan Beulich
2016-04-08 12:18 ` Andrew Cooper [this message]
2016-04-08 22:58 ` Jan Beulich
2016-04-15 17:11 ` Andrew Cooper
2016-04-17 8:22 ` Jan Beulich
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=5707A18E.3030707@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.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.