Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: MIPS Linux List <linux-mips@linux-mips.org>
Subject: Re: [Patch] Fix lookup_dcookie for MIPS o32
Date: Wed, 19 Oct 2005 09:13:28 -0700	[thread overview]
Message-ID: <435670A8.9000402@avtrex.com> (raw)
In-Reply-To: <20051018202654.GB2659@linux-mips.org>

Ralf Baechle wrote:
> On Tue, Oct 18, 2005 at 09:04:49AM -0700, David Daney wrote:
> 
> 
>>The CPU has performance counters, but they cannot trigger interrupts, so 
>>I am just using it in 'timer' mode right now.  I am wondering what would 
>>happen if I added all counter samples at each clock tick.  That is 
>>something I might try when I have a little free time.
> 
> 
> Now that's truly a strange processor - what CPU are you using?
> 

ATI Xilleon X226-A12.  According to my data sheet, there are ten 
counters, but you can only use six at a time.  They are external to the 
4KEc core, and the only operations you can do to them are enable/disable 
counting, reset to zero and read the current values.

The counters count:
I cache hit/miss
D cache hit/miss
TLB hit/miss
JTLB hit/miss
Write merging/not merging

Perhaps I should not worry about them.  Probably hooking up one of the 
high resolution timers would yield more useful profiling information.


> 
>>I had one other problem with my cross built bash where the signal 
>>numbering of the build host was being used instead of the numbering for 
>>the target.  Once I fixed bash and the lookup_dcookie system call, it 
>>seems to work flawlessly.
> 
> 
> That bug is getting a classic.  I've fixed it in ash also - ages ago ...
> 
> I usually try to escape from the horrors of crosscompiling by using a
> decent GHz MIPS system.
> 

Yeah, In a perfect world I would have such a beast.

David Daney

      parent reply	other threads:[~2005-10-19 16:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 21:44 [Patch] Fix lookup_dcookie for MIPS o32 David Daney
2005-10-18 11:45 ` Ralf Baechle
2005-10-18 23:24   ` John Levon
2005-10-18 23:35     ` David Daney
2005-10-18 23:36       ` John Levon
2005-10-19  9:07         ` Geert Uytterhoeven
2005-10-19 10:40           ` Ralf Baechle
2005-10-19 11:21             ` Geert Uytterhoeven
2005-10-19 15:48   ` Thiemo Seufer
2005-10-19 15:55     ` Ralf Baechle
     [not found] ` <20051018115155.GD2656@linux-mips.org>
     [not found]   ` <43551D21.3010500@avtrex.com>
     [not found]     ` <20051018202654.GB2659@linux-mips.org>
2005-10-19 16:13       ` David Daney [this message]

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=435670A8.9000402@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox