From: Eric Blake <eblake@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Gleb Natapov <gleb@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] Intel MPX feature support at Qemu
Date: Fri, 06 Dec 2013 08:09:51 -0700 [thread overview]
Message-ID: <52A1E8BF.30807@redhat.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC829233501409DF5@SHSMSX101.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On 12/06/2013 07:06 AM, Liu, Jinsong wrote:
> Intel has released Memory Protection Extensions (MPX) recently.
> Please refer to http://download-software.intel.com/sites/default/files/319433-015.pdf
>
> These 2 patches are version2 to support Intel MPX at qemu side.
You still aren't threading correctly, which makes it hard to track your
series. Please review http://wiki.qemu.org/Contribute/SubmitAPatch and
make sure your 'git send-email' settings allow for proper threading; a
good way to test that is to first send the patch series to yourself to
ensure your environment is set up correctly.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-12-06 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 14:06 [Qemu-devel] [PATCH v3 0/2] Intel MPX feature support at Qemu Liu, Jinsong
2013-12-06 15:09 ` Eric Blake [this message]
2013-12-06 16:27 ` Liu, Jinsong
2013-12-06 17:21 ` H. Peter Anvin
2013-12-06 15:42 ` Paolo Bonzini
2013-12-06 16:29 ` Liu, Jinsong
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=52A1E8BF.30807@redhat.com \
--to=eblake@redhat.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jinsong.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).