WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] RE: Ping#2: [PATCH] VMX: extend last branch MSR info to cove

To: Jan Beulich <JBeulich@xxxxxxxx>, Haitao Shan <maillists.shan@xxxxxxxxx>
Subject: [Xen-devel] RE: Ping#2: [PATCH] VMX: extend last branch MSR info to cover newer CPU models
From: "Shan, Haitao" <haitao.shan@xxxxxxxxx>
Date: Wed, 9 Nov 2011 17:07:50 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, "Dugger, Donald D" <donald.d.dugger@xxxxxxxxx>
Delivery-date: Wed, 09 Nov 2011 01:11:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4EBA4B72020000780005FC80@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4EB26BB1020000780005EA78@xxxxxxxxxxxxxxxxxxxx> <04F972F38B3C4E4E91C4697DA8BF9F527E41C1F0DD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4EBA4B72020000780005FC80@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acyeu8pfa4jDxPgfTl26PZrsJ0g1kwAAav3g
Thread-topic: Ping#2: [PATCH] VMX: extend last branch MSR info to cover newer CPU models
Frankly speaking, it is also a puzzle to me how to get an accurate
exhaustive list of {Family, Model} given an architecture. Anyway, my thought
is "if any models are listed in any intel public document, that information
should be accurate". I myself does not know that SDMs also contains such
kind of info. 

Thus, I can ACK your patch now.

Shan Haitao

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
> Sent: Wednesday, November 09, 2011 4:44 PM
> To: Haitao Shan; Shan, Haitao
> Cc: Dugger, Donald D; Nakajima, Jun; xen-devel@xxxxxxxxxxxxxxxxxxx; Keir
> Fraser
> Subject: RE: Ping#2: [PATCH] VMX: extend last branch MSR info to cover
> newer CPU models
> 
> >>> On 09.11.11 at 03:56, "Shan, Haitao" <haitao.shan@xxxxxxxxx> wrote:
> > Hi, Jan,
> >
> > I found one useful document in intel website.
> > http://software.intel.com/en-us/articles/intel-processor-identificatio
> > n-with
> > -cpuid-model-and-family-numbers/
> > From the doc, it seems model 45 is not in the list.
> 
> Neither is model 31.
> 
> Which tells us what? That the page isn't up-to-date? After all model 31 is
> referenced in SDM Vol 3 appendix B.4, and model 45 in the same document
> appendix B.7. They're also both in table B-1 of the SDM doc changes (rev
032
> from May this year). Or are you saying the SDM is incorrect?
> 
> At least this answers the question raised in
> http://lists.xensource.com/archives/html/xen-devel/2011-
> 11/msg00411.html
> - 0x2E and 0x2F are supposed to go into the Nehalem/Westmere group then
> for cpuidle purposes.
> 
> Jan
> 
> > Shan Haitao
> >
> >> -----Original Message-----
> >> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
> >> Sent: Thursday, November 03, 2011 5:24 PM
> >> To: Haitao Shan; Shan, Haitao
> >> Cc: Dugger, Donald D; Nakajima, Jun; xen-devel@xxxxxxxxxxxxxxxxxxx;
> >> Keir Fraser
> >> Subject: Ping#2: [PATCH] VMX: extend last branch MSR info to cover
> >> newer CPU models
> >>
> >> VMX: extend last branch MSR info to cover newer CPU models #2
> >>
> >> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
> >>
> >> --- a/xen/arch/x86/hvm/vmx/vmx.c
> >> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> >> @@ -1738,10 +1738,9 @@ static const struct lbr_info *last_branc
> >>          case 23:
> >>              return c2_lbr;
> >>              break;
> >> -        /* Nehalem */
> >> -        case 26: case 30: case 31: case 46:
> >> -        /* Sandy Bridge */
> >> -        case 42: case 45:
> >> +        /* Nehalem/Sandy Bridge */
> >> +        case 26: case 30: case 31: case 37:
> >> +        case 42: case 44: case 45: case 46: case 47:
> >>              return nh_lbr;
> >>              break;
> >>          /* Atom */
> >>
> >>
> 
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>