| To: | David Daney <ddaney@caviumnetworks.com> |
|---|---|
| Subject: | Re: Cavium mips64 perf counters |
| From: | "Giant Sand Fan's" <rampxxxx@gmail.com> |
| Date: | Tue, 27 Apr 2010 10:24:05 +0200 |
| Cc: | linux-mips@linux-mips.org |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=RUgwB2LQ8e3mjguEKqHW5dw3TfqVTjuaFx1p4Bv4xKo=; b=hQfVD03lNUY07caH2W1crykz4kwYbNn9L6IXj+OaMDBqEBGNLduPg4l9tRrIsWMm/B H9nT74yjoa5IAG+sVJEdyaLffs5gBRLcDSjVSA/qEMmD3otzG4tV3q44Kv9jfSFqQ6iv 6zTfFA62gI4O+7YkAHVG1jajOCZXUd966sXbU= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=xkHxf1Pyw3AQWdaXiRLB6ZF6pxdg/vHOza56gvQ/tEvCc+/bx7GofcakSktukqEOnH AQ5F0QYDZNPnjkYAN/BGrRuSNpKMLrGEMhefS1SLsEOzcc/vdLrWz7gn6ZPfUxT0boEr CxEgiATUuStwNZPt4HlKICOLhZ0SrjX3vTUdY= |
| In-reply-to: | <4BD5C7F8.6050406@caviumnetworks.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <l2p417f50831004260640o684d0f8fgf6a3aa60450e329c@mail.gmail.com> <4BD5C7F8.6050406@caviumnetworks.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
0h, thank you David. So can I do something like : A.-) %CPU == (LOG_PERF_CNT_SISSUE)+(LOG_PERF_CNT_DISSUE*2)*100/CVMX_LOG_PERF_CNT_CLK or B.-) %CPU == (CVMX_LOG_PERF_CNT_ISSUE*100)/CVMX_LOG_PERF_CNT_CLK I setup and read perf counters with : mtc0 %0, $25, 0 dmfc0 %0, $25, 1 but I think that I can only read two counters so I can only use "B". ... or I'm totally wrong 2010/4/26 David Daney <ddaney@caviumnetworks.com>: > On 04/26/2010 06:40 AM, Giant Sand Fan's wrote: >> >> Hi, >> >> I'm trying to calculate de CPU load by access the performance counters >> in mips and I haved reading in the cp0 but my problem is that I cannot >> find documentation about the real meaning of these counters : >> >> 1.-LOG_PERF_CNT_NISSUE : żmeans cycle with no issue? >> >> 2.-LOG_PERF_CNT_SISSUE : żmeans cycle with issue? > > Single issue. > >> >> 3.-LOG_PERF_CNT_DISSUE: żmeans cycle with double issue? >> > > That's right. And PERF_CNT_CLK is the number of cycles. > > David Daney > -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 2/2] MIPS: Cleanup of set_uncached_handler(), Wu Zhangjin |
|---|---|
| Next by Date: | use bootmem in platform code on MIPS, Manuel Lauss |
| Previous by Thread: | Re: Cavium mips64 perf counters, David Daney |
| Next by Thread: | [RFC] net/sb1250: setup the pdevice within the soc code, Sebastian Andrzej Siewior |
| Indexes: | [Date] [Thread] [Top] [All Lists] |