All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Lazaridis <slaz@fortresstech.com>
To: Steve Lazaridis <slaz@fortresstech.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	oprofile-list@lists.sourceforge.net, linux-mips@linux-mips.org
Subject: Re: au1550 oprofile
Date: Thu, 23 Mar 2006 12:08:11 -0500	[thread overview]
Message-ID: <4422D5FB.5050806@fortresstech.com> (raw)
In-Reply-To: <441B04AC.3090406@fortresstech.com>

I figured out the problem.
Only I'm not sure if it's actually a bug or not. :)

It seems as if it's in the userspace oprofile tools.

I commented out the following from oprofile/daemon/opd_trans.c   and it 
works fine now.

/* FIXME: this logic is perhaps too harsh? */
if (trans->current->ignored || (trans->last && trans->last->ignored)) {
       verbprintf(vmisc, "in the harsh logic\n");
       goto out;
}


Maybe it's just too harsh for MIPS platforms?  The same version of 
oprofile worked fine on my x86 workstation.


Thanks,
Steve



Steve Lazaridis wrote:
> Thats true,
> But my problem is that timer mode isn't even working
> 
> Ralf Baechle wrote:
>> On Thu, Mar 16, 2006 at 09:22:11PM -0500, Steve Lazaridis wrote:
>>
>>> Has anyone successfully ran oprofile on an au1550?
>>> If so, was it in BigEndian mode?
>>>
>>> Are there any known issues with oprofile on au1xxx platforms?
>>
>> Alchemy processors don't implement performance counters, so there are
>> by definition no issues ;-)  That unfortunately means you're stuck
>> with timer mode.
>>
>>   Ralf

      reply	other threads:[~2006-03-23 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17  2:22 au1550 oprofile Steve Lazaridis
2006-03-17  7:11 ` vsftp -- ping ( two problems) Gowri Satish Adimulam
2006-03-17  9:46   ` Ralf Baechle
2006-03-17 14:56 ` au1550 oprofile Ralf Baechle
2006-03-17 18:49   ` Steve Lazaridis
2006-03-23 17:08     ` Steve Lazaridis [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=4422D5FB.5050806@fortresstech.com \
    --to=slaz@fortresstech.com \
    --cc=linux-mips@linux-mips.org \
    --cc=oprofile-list@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.