From: Venkat K. <ven...@en...> - 2007-11-12 11:31:36
|
Hi Folks, I had installed OProfile 0.9.3 version ( latest ) on my workstation. The Processor is an ARM/Xscale3 processor. I am running Linux version 2.6.18.3 I browsed through the code of OProfile Kernel driver and found that there is support for XScale3. But with the user space tools I found that there is no support for XScale3. I browsed through that code as well and figured out that there are few structures which needs to be updated with XScale3 information other wise it throws an error saying "cpu_type unset is not valid, Force OProfile in timer mode" I updated the structures with XScale3 information and when opcontrol --start is run this error is not shown. (With out these updates when tried to run opcontrol --start, cpu_type error was coming) After the above changes I am able to profile the kernel and applications as well. But after profiling if I run the command "opreport -l" It shows the following two lines followed by the data in the format given below. The output shows the speed as 0 MHz. What does this mean? and it also shows that profiling through timer interrupt ( Deos this mean that the processor though has support performance counters doesn't have enough hardware support to generate the interrupt ). Please Clarify... =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D CPU: CPU with timer interrupt, speed 0 MHz (estimated) Profiling through timer interrupt =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D samples % app name symbol name ................ ................ ................ How will I make sure that the OProfile is profiling precisely? Regards, Venkat --=20 Want an e-mail address like mine? Get a free e-mail account today at www.mail.com! |
From: Maynard J. <may...@us...> - 2007-11-12 14:53:38
|
Venkat Kumar wrote: > Hi Folks, > > > I had installed OProfile 0.9.3 version ( latest ) on my workstation. > > The Processor is an ARM/Xscale3 processor. > > I am running Linux version 2.6.18.3 > > I browsed through the code of OProfile Kernel driver and found that > there is support for XScale3. > > But with the user space tools I found that there is no support for > XScale3. > > I browsed through that code as well and figured out that there are few > structures which needs to be updated with XScale3 information other > wise it throws an error > saying "cpu_type unset is not valid, Force OProfile in timer mode" I > updated the structures with XScale3 information and when opcontrol > --start is run this error is not shown. > (With out these updates when tried to run opcontrol --start, cpu_type > error was coming) > > After the above changes I am able to profile the kernel and > applications as well. Hello, Venkat, Difficult to discern exactly what's wrong without seeing your patch. But these are the things you need to add to userspace oprofile to support a new processor that the kernel already supports: - Do 'opcontrol --init' and see what the kernel assigns to /dev/oprofile/cpu_type. This typically consists of two segments: <arch>/<processor_model> - Create new directory under the existing 'events' directory: events/<arch>/<processor_model>, where '<arch>/<processor_model>' match what the kernel reported as cpu_type. - Add events file and unit_masks file to the new <processor_model> directory - Update events/Makefile.am to include new directory - Update libop/op_cpu_type.c[h], libop/op_events.c, and utils/ophelp.c as needed Good luck. Regards, -Maynard > > But after profiling if I run the command "opreport -l" > It shows the following two lines followed by the data in the format > given below. The output shows the speed as 0 MHz. What does this mean? > and it also shows that profiling through timer interrupt ( Deos this > mean that the processor though has support performance counters > doesn't have enough hardware support to generate the interrupt ). > Please Clarify... > > ======================================================= > CPU: CPU with timer interrupt, speed 0 MHz (estimated) > Profiling through timer interrupt > ======================================================= > > samples % app name symbol name > ................ > ................ > ................ > > How will I make sure that the OProfile is profiling precisely? > > > Regards, > Venkat > > -- > Want an e-mail address like mine? > Get a *free e-mail *account today at www.mail.com > <http://www.mail.com/Product.aspx>! > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ------------------------------------------------------------------------ > > _______________________________________________ > oprofile-list mailing list > opr...@li... > https://lists.sourceforge.net/lists/listinfo/oprofile-list > |
From: William C. <wc...@re...> - 2007-11-13 16:51:34
|
Venkat Kumar wrote: > Hi Folks, > > > I had installed OProfile 0.9.3 version ( latest ) on my workstation. > > The Processor is an ARM/Xscale3 processor. > > I am running Linux version 2.6.18.3 > > I browsed through the code of OProfile Kernel driver and found that > there is support for XScale3. > > But with the user space tools I found that there is no support for XScale3. > > I browsed through that code as well and figured out that there are few > structures which needs to be updated with XScale3 information other wise > it throws an error > saying "cpu_type unset is not valid, Force OProfile in timer mode" I > updated the structures with XScale3 information and when opcontrol > --start is run this error is not shown. > (With out these updates when tried to run opcontrol --start, cpu_type > error was coming) > > After the above changes I am able to profile the kernel and applications > as well. > > But after profiling if I run the command "opreport -l" > It shows the following two lines followed by the data in the format > given below. The output shows the speed as 0 MHz. What does this mean? > and it also shows that profiling through timer interrupt ( Deos this > mean that the processor though has support performance counters doesn't > have enough hardware support to generate the interrupt ). > Please Clarify... > > ======================================================= > CPU: CPU with timer interrupt, speed 0 MHz (estimated) > Profiling through timer interrupt > ======================================================= > > samples % app name symbol name > ................ > ................ > ................ > > How will I make sure that the OProfile is profiling precisely? > > > Regards, > Venkat Which specific kernel/oprofile driver version are you looking at? There doesn't seem to be an arm xscale3 support in either the 2.6.24-rc2 kernel or the oprofile cvs? Is this in a specific distribution? If this is in a specific distribution, you might talk with the vendors of that distribution. Also encourage them to submit those patches up stream. -Will |