All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "gleb@redhat.com" <gleb@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"Ren, Qiaowei" <qiaowei.ren@intel.com>
Subject: Re: [PATCH v2 0/4] X86/KVM: enable Intel MPX for KVM
Date: Thu, 12 Dec 2013 10:43:36 +0100	[thread overview]
Message-ID: <52A98548.9010008@redhat.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC829233501421D73@SHSMSX101.ccr.corp.intel.com>

Il 12/12/2013 06:47, Liu, Jinsong ha scritto:
> Paolo Bonzini wrote:
>> Il 11/12/2013 09:31, Liu, Jinsong ha scritto:
>>> Paolo, comments for version 2?
>>
>> I think I commented that it's fine, I'm just waiting for a rebase on
>> top of the generic patches.
>>
>> Paolo
>>
> 
> Thanks! common MPX definiation patches have been checked in tip tree (both Qiaowei and I use that definiations):
> http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=191f57c137bcce0e3e9313acb77b2f114d15afbb
> http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=e7d820a5e549b3eb6c3f9467507566565646a669

Ok, can you rebase and resend?

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "gleb@redhat.com" <gleb@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Ren, Qiaowei" <qiaowei.ren@intel.com>
Subject: Re: [PATCH v2 0/4] X86/KVM: enable Intel MPX for KVM
Date: Thu, 12 Dec 2013 10:43:36 +0100	[thread overview]
Message-ID: <52A98548.9010008@redhat.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC829233501421D73@SHSMSX101.ccr.corp.intel.com>

Il 12/12/2013 06:47, Liu, Jinsong ha scritto:
> Paolo Bonzini wrote:
>> Il 11/12/2013 09:31, Liu, Jinsong ha scritto:
>>> Paolo, comments for version 2?
>>
>> I think I commented that it's fine, I'm just waiting for a rebase on
>> top of the generic patches.
>>
>> Paolo
>>
> 
> Thanks! common MPX definiation patches have been checked in tip tree (both Qiaowei and I use that definiations):
> http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=191f57c137bcce0e3e9313acb77b2f114d15afbb
> http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=e7d820a5e549b3eb6c3f9467507566565646a669

Ok, can you rebase and resend?

Paolo


WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "gleb@redhat.com" <gleb@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"Ren, Qiaowei" <qiaowei.ren@intel.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/4] X86/KVM: enable Intel MPX for KVM
Date: Thu, 12 Dec 2013 10:43:36 +0100	[thread overview]
Message-ID: <52A98548.9010008@redhat.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC829233501421D73@SHSMSX101.ccr.corp.intel.com>

Il 12/12/2013 06:47, Liu, Jinsong ha scritto:
> Paolo Bonzini wrote:
>> Il 11/12/2013 09:31, Liu, Jinsong ha scritto:
>>> Paolo, comments for version 2?
>>
>> I think I commented that it's fine, I'm just waiting for a rebase on
>> top of the generic patches.
>>
>> Paolo
>>
> 
> Thanks! common MPX definiation patches have been checked in tip tree (both Qiaowei and I use that definiations):
> http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=191f57c137bcce0e3e9313acb77b2f114d15afbb
> http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=e7d820a5e549b3eb6c3f9467507566565646a669

Ok, can you rebase and resend?

Paolo

  reply	other threads:[~2013-12-12  9:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1386394315-48984-1-git-send-email-jinsong.liu@intel.com>
2013-12-11  8:31 ` [PATCH v2 0/4] X86/KVM: enable Intel MPX for KVM Liu, Jinsong
2013-12-11  8:31   ` [Qemu-devel] " Liu, Jinsong
2013-12-11  9:53   ` Paolo Bonzini
2013-12-11  9:53     ` [Qemu-devel] " Paolo Bonzini
2013-12-12  5:47     ` Liu, Jinsong
2013-12-12  5:47       ` [Qemu-devel] " Liu, Jinsong
2013-12-12  5:47       ` Liu, Jinsong
2013-12-12  9:43       ` Paolo Bonzini [this message]
2013-12-12  9:43         ` [Qemu-devel] " Paolo Bonzini
2013-12-12  9:43         ` Paolo Bonzini
2013-12-12 11:09         ` Liu, Jinsong
2013-12-12 11:09           ` [Qemu-devel] " Liu, Jinsong
2014-01-20 14:35           ` Paolo Bonzini
2014-01-20 14:35             ` [Qemu-devel] " Paolo Bonzini
2014-01-21 15:25             ` Liu, Jinsong
2014-01-21 15:25               ` [Qemu-devel] " Liu, Jinsong
2014-01-21 16:33               ` Paolo Bonzini
2014-01-21 16:33                 ` [Qemu-devel] " Paolo Bonzini
2014-01-21 17:26                 ` Liu, Jinsong
2014-01-21 17:26                   ` [Qemu-devel] " 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=52A98548.9010008@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 \
    --cc=qiaowei.ren@intel.com \
    /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.