From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tim Deegan <tim@xen.org>
Cc: boris.ostrovsky@oracle.com, xen-devel@lists.xensource.com,
jun.nakajima@intel.com, jbeulich@suse.com
Subject: Re: [PATCH 1/2] x86/Intel: Provide comments for which model is what.
Date: Fri, 1 Mar 2013 10:30:42 -0500 [thread overview]
Message-ID: <20130301153042.GC8757@phenom.dumpdata.com> (raw)
In-Reply-To: <20130301144508.GB40913@ocelot.phlegethon.org>
On Fri, Mar 01, 2013 at 02:45:08PM +0000, Tim Deegan wrote:
> At 09:31 -0500 on 01 Mar (1362130307), Konrad Rzeszutek Wilk wrote:
> > + case 15: /* original 65 nm celeron/pentium/core2/xeon, "Merom"/"Conroe" */
> > + case 23: /* current 45 nm celeron/core2/xeon "Penryn"/"Wolfdale" */
>
> No opinion about the patch in general, but it might be better not to say
> "current" here, at least without attaching a date.
OK. How about this:
commit 7de84d0668df18977ebc9c299d6562676e76dbd5
Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Date: Fri Mar 1 09:21:35 2013 -0500
x86/Intel: Provide comments for which model is what.
[v1: Tim suggested to remove 'current' from the comments]
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
diff --git a/xen/arch/x86/hvm/vmx/vpmu_core2.c b/xen/arch/x86/hvm/vmx/vpmu_core2.c
index 2cef2d6..5d22a70 100644
--- a/xen/arch/x86/hvm/vmx/vpmu_core2.c
+++ b/xen/arch/x86/hvm/vmx/vpmu_core2.c
@@ -738,16 +738,16 @@ int vmx_vpmu_initialise(struct vcpu *v, unsigned int vpmu_flags)
{
switch ( cpu_model )
{
- case 15:
- case 23:
- case 26:
- case 29:
- case 42:
- case 45:
- case 46:
- case 47:
- case 58:
- case 62:
+ case 15: /* original 65 nm celeron/pentium/core2/xeon, "Merom"/"Conroe" */
+ case 23: /* 45 nm celeron/core2/xeon "Penryn"/"Wolfdale" */
+ case 26: /* 45 nm nehalem, "Bloomfield" */
+ case 29: /* six-core 45 nm xeon "Dunnington" */
+ case 42: /* SandyBridge */
+ case 45: /* SandyBridge, "Romely-EP" */
+ case 46: /* 45 nm nehalem-ex, "Beckton" */
+ case 47: /* 32 nm Xeon E7 */
+ case 58: /* IvyBridge */
+ case 62: /* IvyBridge EP */
ret = core2_vpmu_initialise(v, vpmu_flags);
if ( !ret )
vpmu->arch_vpmu_ops = &core2_vpmu_ops;
next prev parent reply other threads:[~2013-03-01 15:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 14:31 [PATCH] Add missing Intel models to VPMU Konrad Rzeszutek Wilk
2013-03-01 14:31 ` [PATCH 1/2] x86/Intel: Provide comments for which model is what Konrad Rzeszutek Wilk
2013-03-01 14:45 ` Tim Deegan
2013-03-01 15:30 ` Konrad Rzeszutek Wilk [this message]
2013-03-01 15:50 ` Jan Beulich
2013-03-01 15:55 ` Tim Deegan
2013-03-01 14:31 ` [PATCH 2/2] x86/Intel: Add missing Merom, Westmere, and Nehelem models Konrad Rzeszutek Wilk
2013-03-01 15:49 ` Simon Rowe
2013-03-01 15:53 ` Jan Beulich
2013-03-01 16:40 ` Konrad Rzeszutek Wilk
2013-03-01 18:37 ` Nakajima, Jun
2013-03-04 8:15 ` Dietmar Hahn
2013-03-04 18:01 ` Konrad Rzeszutek Wilk
2013-03-05 13:49 ` Dietmar Hahn
2013-03-05 14:00 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2013-03-04 18:04 [PATCH] comments in the vpmu_core2 code and additional cpuids (v2) Konrad Rzeszutek Wilk
2013-03-04 18:04 ` [PATCH 1/2] x86/Intel: Provide comments for which model is what Konrad Rzeszutek Wilk
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=20130301153042.GC8757@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=tim@xen.org \
--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 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.