From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Donald D Dugger <donald.d.dugger@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH] x86: add Ivy Bridge model numbers to model specific MSR handling
Date: Mon, 06 Feb 2012 08:36:18 +0000 [thread overview]
Message-ID: <CB554182.2A7AC%keir.xen@gmail.com> (raw)
In-Reply-To: <4F300E050200007800071664@nat28.tlf.novell.com>
On 06/02/2012 16:29, "Jan Beulich" <JBeulich@suse.com> wrote:
> This is model 0x3a (decimal 58) as per the most recent SDM.
>
> In vPMU code, also add a forgotten earlier model.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Fine by me with an appropriate Ack from Intel.
K.
> --- a/xen/arch/x86/acpi/cpu_idle.c
> +++ b/xen/arch/x86/acpi/cpu_idle.c
> @@ -106,6 +106,8 @@ static void do_get_hw_residencies(void *
>
> switch ( c->x86_model )
> {
> + /* Ivy bridge */
> + case 0x3A:
> /* Sandy bridge */
> case 0x2A:
> case 0x2D:
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -1751,6 +1751,8 @@ static const struct lbr_info *last_branc
> case 37: case 44: case 47:
> /* Sandy Bridge */
> case 42: case 45:
> + /* Ivy Bridge */
> + case 58:
> return nh_lbr;
> break;
> /* Atom */
> --- a/xen/arch/x86/hvm/vmx/vpmu_core2.c
> +++ b/xen/arch/x86/hvm/vmx/vpmu_core2.c
> @@ -623,8 +623,10 @@ int vmx_vpmu_initialise(struct vcpu *v)
> case 26:
> case 29:
> case 42:
> + case 45:
> case 46:
> case 47:
> + case 58:
> vpmu->arch_vpmu_ops = &core2_vpmu_ops;
> return 0;
> }
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-02-06 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 16:29 [PATCH] x86: add Ivy Bridge model numbers to model specific MSR handling Jan Beulich
2012-02-06 8:36 ` Keir Fraser [this message]
2012-02-09 3:36 ` Zhang, Xiantao
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=CB554182.2A7AC%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=donald.d.dugger@intel.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.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 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).