From: "Mike C. Ward" <mward@pioneer-pra.com>
To: "'David Daney'" <ddaney@avtrex.com>, <linux-mips@linux-mips.org>
Subject: RE: Where is op_model_mipsxx.c ?
Date: Fri, 7 Oct 2005 11:13:02 -0700 [thread overview]
Message-ID: <020b01c5cb6a$c2251830$5502020a@eo> (raw)
In-Reply-To: <4343525A.6080605@avtrex.com>
I created an op_model file for the r5K core in a MIPS32 kernel.
details are at
http://oss.pioneer-pra.com/oprofile/
I have not had a chance to test it on a real 2.6 kernel yet, it
was back-ported from 2.6.11 into 2.4.25.
Mike
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of David Daney
> Sent: Tuesday, October 04, 2005 9:11 PM
> To: linux-mips@linux-mips.org
> Subject: Where is op_model_mipsxx.c ?
>
>
> I noticed this in the Makefile for the OProfile directory for mips:
>
> oprofile-$(CONFIG_CPU_MIPS32_R1) += op_model_mipsxx.o
>
> The file op_model_mipsxx.c does not seem to exist. Which
> implies to me
> that someone was working on making it work for MIPS32, but
> didn't quite
> finish.
>
> I want to start hacking on OProfile for a MIPS32 based system and
> thought it might make a nice starting point.
>
> If the missing file exists would its author mind making it
> available to me?
>
> Thanks,
> David Daney
>
>
WARNING: multiple messages have this Message-ID (diff)
From: "Mike C. Ward" <mward@pioneer-pra.com>
To: 'David Daney' <ddaney@avtrex.com>, linux-mips@linux-mips.org
Subject: RE: Where is op_model_mipsxx.c ?
Date: Fri, 7 Oct 2005 11:13:02 -0700 [thread overview]
Message-ID: <020b01c5cb6a$c2251830$5502020a@eo> (raw)
Message-ID: <20051007181302.2iopSsnEvg0pFyVuD0ZG_h3fPRjyDFrmUzYhs6z3QAM@z> (raw)
In-Reply-To: <4343525A.6080605@avtrex.com>
I created an op_model file for the r5K core in a MIPS32 kernel.
details are at
http://oss.pioneer-pra.com/oprofile/
I have not had a chance to test it on a real 2.6 kernel yet, it
was back-ported from 2.6.11 into 2.4.25.
Mike
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of David Daney
> Sent: Tuesday, October 04, 2005 9:11 PM
> To: linux-mips@linux-mips.org
> Subject: Where is op_model_mipsxx.c ?
>
>
> I noticed this in the Makefile for the OProfile directory for mips:
>
> oprofile-$(CONFIG_CPU_MIPS32_R1) += op_model_mipsxx.o
>
> The file op_model_mipsxx.c does not seem to exist. Which
> implies to me
> that someone was working on making it work for MIPS32, but
> didn't quite
> finish.
>
> I want to start hacking on OProfile for a MIPS32 based system and
> thought it might make a nice starting point.
>
> If the missing file exists would its author mind making it
> available to me?
>
> Thanks,
> David Daney
>
>
next prev parent reply other threads:[~2005-10-07 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 4:11 Where is op_model_mipsxx.c ? David Daney
2005-10-05 10:44 ` Ralf Baechle
2005-10-25 11:25 ` Matej Kupljen
2005-10-25 15:01 ` David Daney
2005-10-26 6:35 ` Matej Kupljen
2005-10-26 12:15 ` Ralf Baechle
2005-10-07 18:13 ` Mike C. Ward [this message]
2005-10-07 18:13 ` Mike C. Ward
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='020b01c5cb6a$c2251830$5502020a@eo' \
--to=mward@pioneer-pra.com \
--cc=ddaney@avtrex.com \
--cc=linux-mips@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