lkml.org 
[lkml]   [2012]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH V6 08/13] perf: Add Sandy Bridge-EP uncore support
    On 06/16/2012 01:10 AM, Peter Zijlstra wrote:
    > On Fri, 2012-06-15 at 14:31 +0800, Yan, Zheng wrote:
    >> +static struct event_constraint snbep_uncore_r2pcie_constraints[] = {
    >> + UNCORE_EVENT_CONSTRAINT(0x10, 0x3),
    >> + UNCORE_EVENT_CONSTRAINT(0x11, 0x3),
    >> + UNCORE_EVENT_CONSTRAINT(0x12, 0x1),
    >> + UNCORE_EVENT_CONSTRAINT(0x23, 0x3),
    >> + UNCORE_EVENT_CONSTRAINT(0x24, 0x3),
    >> + UNCORE_EVENT_CONSTRAINT(0x25, 0x3),
    >> + UNCORE_EVENT_CONSTRAINT(0x26, 0x3),
    >> + UNCORE_EVENT_CONSTRAINT(0x32, 0x3),
    >> + UNCORE_EVENT_CONSTRAINT(0x33, 0x3),
    >> + UNCORE_EVENT_CONSTRAINT(0x34, 0x3),
    >> + EVENT_CONSTRAINT_END
    >> +};
    >
    > My E5-2600 Uncore Perf. Mon. Guide, March 2012 (Ref.# 327043-001)
    > doesn't seem to list events 0x26 and up.
    >
    > I'm staring at 2.8.5, table 2-108.
    >
    > Is my document out-dated or what's up?
    >
    > the r3qpi table seems to match, but the cbox one is funny again, event
    > 0x01 doesn't appear in the doc, nor does 0x3b, 0x38, 0x23.
    >
    Sorry, my document is out-dated. These events were listed in the old
    document. should we remove them ?

    > FWIW, cbox event constraint 0x1f needs to be an
    > EVENT_CONSTRAINT_OVERLAP, see the comment near that macro definition.
    >
    thanks for reminding

    Regards
    Yan, Zheng


    \
     
     \ /
      Last update: 2012-06-18 04:21    [W:4.111 / U:0.236 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site