From: Paolo Bonzini <pbonzini@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>,
"'qemu-devel@nongnu.org'" <qemu-devel@nongnu.org>,
"'kvm@vger.kernel.org'" <kvm@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Cc: "Mallick, Asit K" <asit.k.mallick@intel.com>,
"'gleb@redhat.com'" <gleb@redhat.com>,
"'hpa@zytor.com'" <hpa@zytor.com>
Subject: Re: [Qemu-devel] [PATCH] target-i386: bugfix of Intel MPX
Date: Mon, 03 Mar 2014 09:34:25 +0100 [thread overview]
Message-ID: <53143E91.4070900@redhat.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC82923350152FC71@SHSMSX101.ccr.corp.intel.com>
Il 03/03/2014 06:24, Liu, Jinsong ha scritto:
> From 3a7783cd9a0556787809d3d5ecb5f2b85dd9fc02 Mon Sep 17 00:00:00 2001
> From: Liu Jinsong <jinsong.liu@intel.com>
> Date: Mon, 3 Mar 2014 18:56:39 +0800
> Subject: [PATCH] target-i386: bugfix of Intel MPX
>
> The correct size of cpuid 0x0d sub-leaf 4 is 0x40, not 0x10.
> This is confirmed by Anvin H Peter and Mallick Asit K.
>
> Signed-off-by: Liu Jinsong <jinsong.liu@intel.com>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: Asit K Mallick <asit.k.mallick@intel.com>
> ---
> target-i386/cpu.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
> index 0e8812a..9f69d7e 100644
> --- a/target-i386/cpu.c
> +++ b/target-i386/cpu.c
> @@ -339,7 +339,7 @@ static const ExtSaveArea ext_save_areas[] = {
> [3] = { .feature = FEAT_7_0_EBX, .bits = CPUID_7_0_EBX_MPX,
> .offset = 0x3c0, .size = 0x40 },
> [4] = { .feature = FEAT_7_0_EBX, .bits = CPUID_7_0_EBX_MPX,
> - .offset = 0x400, .size = 0x10 },
> + .offset = 0x400, .size = 0x40 },
> };
>
> const char *get_register_name_32(unsigned int reg)
>
Thanks, applying to uq/master.
Paolo
prev parent reply other threads:[~2014-03-03 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 5:24 [Qemu-devel] [PATCH] target-i386: bugfix of Intel MPX Liu, Jinsong
2014-03-03 8:34 ` 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=53143E91.4070900@redhat.com \
--to=pbonzini@redhat.com \
--cc=asit.k.mallick@intel.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).