From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/2] oprofile support for ppc750
Date: Wed, 07 Jan 2009 13:52:34 +1100 [thread overview]
Message-ID: <1231296754.14860.51.camel@pasglop> (raw)
In-Reply-To: <1231246535-13151-1-git-send-email-opurdila@ixiacom.com>
On Tue, 2009-01-06 at 14:55 +0200, Octavian Purdila wrote:
> Adds oprofile support for ppc750. ppc750 performance counters
> interface is similar with G4, but it only has 4 performance counters
> instead of 6.
>
> I tested this on a PPC750GX and it seems to work fine.
I'm not too sure about using the same model as 74xx... I have some
patches that haven't been released yet from Jack Miller to implement the
full OP support for 750 but they appear to cause crashes.
There is a known HW bug in various 750's that basically make the
performance interrupt unuseable. I -think- it may have been fixed in the
very latest revision of the 750CL though but I'm not sure.
Cheers,
Ben.
next prev parent reply other threads:[~2009-01-07 2:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 12:55 [PATCH 0/2] oprofile support for ppc750 Octavian Purdila
2009-01-06 12:55 ` [PATCH 1/2] powerpc: G4 oprofile: variable number of counters Octavian Purdila
2009-02-04 5:22 ` Benjamin Herrenschmidt
2009-02-24 12:09 ` Octavian Purdila
2009-02-24 12:09 ` [PATCH v2 " Octavian Purdila
2009-02-24 12:09 ` [PATCH v2 2/2] powerpc: oprofile: enable support for ppc750 processors Octavian Purdila
2009-02-26 22:30 ` Andy Fleming
2009-02-26 23:13 ` Benjamin Herrenschmidt
2009-02-27 11:57 ` Octavian Purdila
2009-01-06 12:55 ` [PATCH " Octavian Purdila
2009-03-04 4:47 ` Benjamin Herrenschmidt
2009-03-04 12:02 ` Octavian Purdila
2009-01-07 2:52 ` Benjamin Herrenschmidt [this message]
2009-01-07 12:17 ` [PATCH 0/2] oprofile support for ppc750 Octavian Purdila
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=1231296754.14860.51.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=opurdila@ixiacom.com \
/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;
as well as URLs for NNTP newsgroup(s).