From: Paolo Bonzini <pbonzini@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>,
"'kvm@vger.kernel.org'" <kvm@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'qemu-devel@nongnu.org'" <qemu-devel@nongnu.org>
Cc: "'gleb@redhat.com'" <gleb@redhat.com>, "'hpa@zytor.com'" <hpa@zytor.com>
Subject: Re: [PATCH v5 3/3] KVM: x86: Enable Intel MPX for guest
Date: Mon, 24 Feb 2014 17:40:57 +0100 [thread overview]
Message-ID: <530B7619.2050805@redhat.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC82923350150F2D0@SHSMSX101.ccr.corp.intel.com>
Il 24/02/2014 16:37, Liu, Jinsong ha scritto:
> So patch v5 would be applied except you will remove the incorrect
> hunk, and you will send a patch strengthenning guest_supported_xcr0?
Yes.
Paolo
prev parent reply other threads:[~2014-02-24 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 10:58 [PATCH v5 3/3] KVM: x86: Enable Intel MPX for guest Liu, Jinsong
2014-02-24 11:13 ` Paolo Bonzini
2014-02-24 15:37 ` Liu, Jinsong
2014-02-24 16:40 ` Paolo Bonzini [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=530B7619.2050805@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jinsong.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).