Will:
We are working on 970 support. There is a difference in the 970 versus power 4 system. Architecturally the systems are very similar. However, they did not keep the register bit definitions the same between the two architectures. Hence, you have different mmcr register values for the same group of events. This results in having to have a unique set of event files. That is really the only difference for Oprofile.
Carl Love
William Cohen <wcohen <at> nc.rr.com>
William Cohen <wcohen <at> nc.rr.com> Sent by: oprofile-list-admin <at> lists.sourceforge.net
10/06/2004 08:30 AM
|
To
|
maynardj <at> us.ltcfwd.linux.ibm.com |
cc
|
oprofile-list <at> lists.sourceforge.net |
Subject
|
Re: New and improved patch for Power4 and Power5 |
|
Maynard P. Johnson wrote:
> John Levon wrote:
>
>> On Tue, Sep 14, 2004 at 12:22:30PM -0500, Maynard P. Johnson wrote:
>>
>>
>>> Here's that patch with the change in opcontrol to use a for-loop.
>>>
>>
>>
>> BTW, changelogs inline in the email from now on please. I took pity the
>> first time :)
>
> John,
> OK, will do. As you guessed, I'm a newbie at this. Thanks for the help.
>
> As I mentioned, I will write up some documentation on the new function
> to be added to sections of the oprofile user manual. One of the pieces
> of information to be documented is the specific kernel version that is
> required. My colleague, Carl Love, has been working that end of things,
> but as of today, not all changes have gotten into the mainline kernel
> yet. Once we have that info, I'll send you the documentation updates.
> Do you want the doc updates in the form of a patch? The oprofile
> website states "You will need to have an XSL stylesheets installation
> (and xsltproc etc.) installed to change the documentation." Can anyone
> point me to any place where I can find out more about how to do this?
>
> Thanks.
> Regards,
> Maynard
>
Looking through the oprofile code for the kernel for the ppc64
oprofile support oprof_ppc64_ops.cpu_type can be set to the following
in arch/ppc64/oprofile/common.c:
"ppc64/power3";
"ppc64/rs64";
"ppc64/power4";
"ppc64/970";
"ppc64/power5";
The patch only handles "ppc64/power4" and "ppc64/power5". On one
machine got:
# more /dev/oprofile/cpu_type
ppc64/970
As a result got non-helpful answer (should print out the reported cpu_type):
# op_help
cpu_type '(null)' is not valid
Are there similar patches for the power3, rs64, and 970? Is the 970 the
same as power4? Why the distinction between power4 and 970 in the
kernel's oprofile driver?
-Will
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
oprofile-list mailing list
oprofile-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oprofile-list