[Top] [All Lists]

RE: Oprofile on sibyte 2.4.18 kernel

To: "Shanthi Kiran Pendyala (skiranp)" <>
Subject: RE: Oprofile on sibyte 2.4.18 kernel
From: "Mark E Mason" <>
Date: Tue, 11 Apr 2006 16:29:03 -0700
Cc: "linux-mips" <>
Original-recipient: rfc822;
Thread-index: AcZamdRoKUMjWTsKT5ersblLdXL9owCa8JOQACmOKlAAA+V1oAAA4vMQ
Thread-topic: Oprofile on sibyte 2.4.18 kernel

> -----Original Message-----
> From: Shanthi Kiran Pendyala (skiranp) [] 
> Sent: Tuesday, April 11, 2006 4:09 PM
> To: Mark E Mason
> Cc: linux-mips
> Subject: RE: Oprofile on sibyte 2.4.18 kernel
> Hi Mark,
> Thx for the info.
> The doc I have has the title 1250_1125-UM100-RDS.pdf. I went 
> back to docsafe And looked for the sb1-um100-rds.pdf doc that 
> you mention. 

Ah - got it.  What you're looking at here is the table for the SOC
performance counters, which aren't currently supported by oprofile.  If
you compare the two, the SOC performance counters deal with activity on
the system Z-bus, the core performance counters deal with processor
cycles, instruction execution, L1 cache activity and the like.

> I thought sb1 is the core and if two of these cores are 
> present it is labelled 1250 and If only one is present it is 
> marketed as 1125 ? Is my understanding wrong ?

This is correct.  From the documentation port of view, all of the "core
stuff" is in the SB1-UM100-RDS.pdf manual, the "SOC stuff" is in the
1250_1125_UM100-RDS.pdf manual.  At this point, oprofile only supports
the core performance counters.

> Let me look at this document and see if it answers my questions.
> Also, yes I was looking at 2.6 git tree, not the CVS tree as 
> I said below.. Sorry about That.

Not a problem.  Please let us know if you have any more questions.


<Prev in Thread] Current Thread [Next in Thread>