RE: oprofile support for PPC_E5500

"Beaman, Thomas" <[email protected]>
Newsgroups gmane.linux.oprofile
Message-ID <1302F7310B9ED04A864E1F2C0AA459BB2A6EBC87@USA7109MB003.na.xerox.net>

> -----Original Message-----
> From: Michael Petlan [mailto:[email protected]]
> Sent: Tuesday, July 12, 2016 4:48 PM
> To: Beaman, Thomas
> Cc: William Cohen; [email protected]
> Subject: RE: oprofile support for PPC_E5500
> 
> On Tue, 12 Jul 2016, Beaman, Thomas wrote:
> >
> >>
> >> Hi Tom,
> >>
> >> Thanks for making the request to Windriver for the e6500 oprofile patch.
> >>
> >> Are there similar special patches in kernel being used to allow
> >> access to the
> >> e5500 performance monitoring hardware?  I see references to e500 and
> >> e6500 in the mainline kernel (linux/arch/power/perf/e500-pmu.c and
> >> linux/arch/power/perf/e6500-pmu.c, but don't see anything for e5500.
> >> Does "perf list" work and list out events thave "[Hardware event]" or
> >> "[Kernel PMU event]" on the line?  If the kernel support isn't there,
> >> then changes to the user-space oprofile isn't make much of a difference.
> >>
> >> -Will
> >
> >
> > Hi Will,
> >
> > So far I am only using Michaels patch plus a few hand edits I make, which
> allows detection of the cpu.
> >
> > I have attached the output of the "perf list" command.  It does have
> > some Hardware Events listed
> >
> > Tom
> >
> 
> Since the `perf list` shows stalled-cycles-frontend and stalled-cycles-backend
> events, it seems it does not use the e6500-pmu.c file, since these events are
> specified in e500-pmu.c only.
> 
> Tom, the question was whether WindRiver has some kernel patches for
> e5500 support or not.
> 
> You may also try to see which PMU drivers are present in kallsyms:
> 
> cat /proc/kallsyms | grep pmu | grep init
> 
> If you see e5500 there, your kernel probably has some WindRiver-specific
> patch, since there is probably no init_e5500_pmu in the upstream kernel.
> 
> Michael

Hi Michael,  

There are no specific WindRiver patches that I can see for the e5500 and there is no init_e5500 in kallsyms. How do you think we should proceed ?  

Thanks,
Tom

root@miopqt_250:~# cat /proc/kallsyms | grep pmu | grep init
c000000000059de8 t .fsl_emb_pmu_event_init
c00000000005acf0 t .init_e500_pmu
c00000000005ade4 t .init_e6500_pmu
c000000000c51f10 t __initcall_init_e500_pmuearly
c000000000c51f18 t __initcall_init_e6500_pmuearly
c000000000d3e480 d fsl_emb_pmu_event_init
c000000000d3e5b8 d init_e500_pmu
c000000000d3e5e8 d init_e6500_pmu



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.