From: William C. <wc...@re...> - 2005-07-26 21:12:19
|
Today I was trying stuff out on a ppc64 (iseries) machine where the kernel returns "ppc64/rs64" for /dev/oprofile/cpu_type. Unfortunately, there doesn't seem to be any entries for it in the userspace oprofile. Do any of the ppc64 experts have a patch or a pointer documentation on the performance monitoring hardware for this family of ppc64 processors? -Will |
From: Maynard J. <may...@us...> - 2005-07-27 21:06:59
|
William Cohen wrote: > Today I was trying stuff out on a ppc64 (iseries) machine where the > kernel returns "ppc64/rs64" for /dev/oprofile/cpu_type. Unfortunately, > there doesn't seem to be any entries for it in the userspace oprofile. > Do any of the ppc64 experts have a patch or a pointer documentation on > the performance monitoring hardware for this family of ppc64 processors? > > -Will Hi, Will, No patch for rs64, I'm afraid. However, if the kernel support added by Anton back in 2004 is golden, the hardest part to porting oprofile to this processor is laying hands on the event and group information. I just made contact with someone here at IBM who can provide that information. We need to know exactly which model of rs64 you have. Could you tell us the speed at which the processor runs? That's one way for us to determine the model. Once we know that, I can send you the appropriate event and group information. I'll be glad to help as much as I can, but unfortunately, I just don't have the bandwidth right now to do this by myself. Regards, Maynard > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > oprofile-list mailing list > opr...@li... > https://lists.sourceforge.net/lists/listinfo/oprofile-list > |
From: John L. <le...@mo...> - 2005-07-27 21:19:08
|
On Wed, Jul 27, 2005 at 04:07:11PM -0500, Maynard Johnson wrote: > >Today I was trying stuff out on a ppc64 (iseries) machine where the > >kernel returns "ppc64/rs64" for /dev/oprofile/cpu_type. Unfortunately, > > just made contact with someone here at IBM who can provide that > information. We need to know exactly which model of rs64 you have. > Could you tell us the speed at which the processor runs? That's one way If the events differ between rs64 models, then the kernel is broken - it must return different cpu_type entries for the different models. It shouldn't even be returning a cpu_type unrecognised by userspace, that's just broken. regards john |
From: William C. <wc...@re...> - 2005-07-27 21:30:00
|
John Levon wrote: > On Wed, Jul 27, 2005 at 04:07:11PM -0500, Maynard Johnson wrote: > > >>>Today I was trying stuff out on a ppc64 (iseries) machine where the >>>kernel returns "ppc64/rs64" for /dev/oprofile/cpu_type. Unfortunately, >> >>just made contact with someone here at IBM who can provide that >>information. We need to know exactly which model of rs64 you have. >>Could you tell us the speed at which the processor runs? That's one way > > > If the events differ between rs64 models, then the kernel is broken - it > must return different cpu_type entries for the different models. > > It shouldn't even be returning a cpu_type unrecognised by userspace, > that's just broken. > > regards > john The cpu_type needs to UNIQUELY identify the processor's events. Is the situation where the newer (higher speed) processors have fixed the events and are a pure super set of the older processors? I noticed in the identifying logic that there were several different types of processors lumped into the "ppc64/rs64". If the processors have different events, then there needs to be different identifiers for each. For example the "ia64/itanium" and "ia64/itanium2". -Will |