Re: Re : Reg: Sample file creation for the event PC_CHANGE on ARMV6 (Santhosh)

[Maynard J. <may...@us...>]

Santhosh wrote:
> Hi Maynard,
> 
> While debugging the source code "arch/arm/oprofile" , observed that "armv6_pmu_start()" (in op_model_v6.c) calls "arm11_request_interrupts()" (in op_model_arm11_core.c) function. and arguments passing to "arm11_request_interrupts()" are '0' & '0' , so in that function "request_irq()" , wont get called . which in turn  calls "arm11_pmu_interrupt()", this calls "oprofile_add_sample()",

So this implies CONFIG_ARCH_OMAP2 is undefined.  This is an arm-specific config option, but I don't speak arm.  I'm cc'ing Richard Purdie, since he's the maintainer of arm bits for OProfile.

-Maynard
> 
> So request_irq is not getting call. 
> I am not sure request line '0' can be used for the oprofile ? . I suspect this might be a problem. 
> Please have a look.  and comment on this.
> 
> Santhosh
> 
> 
>> -----Original Message-----
>> From: may...@us...
>> Sent: Wed, 27 Aug 2008 10:48:10 -0500
>> To: san...@in...
>> Subject: Re: Re : Reg: Sample file creation for the event PC_CHANGE on
>> ARMV6 (Santhosh)
>>
>> Santhosh wrote:
>>> HI Maynard,
>>> I ran "opcontrol --start" command too. But Profiler not generating
>>> sample files for any event.
>> It might be best to start fresh, just to make sure you're not
>> inadvertently using some options that are cached in
>> /root/.oprofile/daemonrc.  Try the following:
>> 1. opcontrol --deinit
>> 2. rm /root/.oprofile/daemonrc
>> 3. opcontrol --init
>> 4. opcontrol --no-vmlinux
>> 5. opcontrol --start --verbose (This should start profiling using the
>> default CPU_CYCLES event.  You'll also get a verbose output in the
>> oprofiled.log)
>> 6. Run your application
>> 7. opcontrol --stop
>> 8. opreport -l
>>
>> If you still get "no samples found", look at your system log (dmesg) and
>> oprofiled.log to see if you find any error messages.
>>
>>> Application Oprofile will read the kernel samples and creates sample
>>> files . Generally kernel only will collects the samples. Am i right ?
>> Yes, the kernel driver collects the samples and the userspace oprofile
>> daemon reads them from the kernel buffer and persists them to sample
>> files.
>>
>>> Or can anyone clarify this,  what is difference in capturing events when
>>> profiler uses timer interrupt & normal performance counters?
>> See OProfile manual (http://oprofile.sourceforge.net/doc/index.html),
>> section 3.4 "Configuration details".
>>
>>> Thanks & Regards,
>>> Santhosh
>>>
>>>> -----Original Message-----
>>>> From: may...@us...
>>>> Sent: Mon, 25 Aug 2008 15:01:54 -0500
>>>> To: san...@in...
>>>> Subject: Re: Re : Reg: Sample file creation for the event PC_CHANGE on
>>>> ARMV6 (Santhosh)
>>>>
>>>> Santhosh wrote:
>>>>> Hi,
>>>>> I followed Mr.Jean commands of execution , But no luck this time also.
>>>>> i
>>>>> am useing ARM V6 - revision 4 board and TI-OMAP2430 SDP Target .
>>>>>
>>>>> I followed below mentioned commands.
>>>>> opcontrol --reset
>>>>> opcontrol --init
>>>>> opcontrol --no-vmlinux
>>>>> opcontrol -e PC_CHANGE:500:0:1:1
>>>>> opcontrol --start-daemon
>>>>> opcontrol --start
>>>> In your first posting, your list of commands didn't include 'opcontrol
>>>> --start' which, if your email was accurate, would account for no
>>>> samples.
>>>>> opcontrol --dump
>>>>> opcontrol --stop
>>>>> opcontrol --shutdown
>>>>> opcontrol --deinit
>>>>> opreport -l
>>>>>
>>>>> But no luck.
>>>>>
>>>>> Is --init ( to initialize the CPU for profiling), --no-vmlinux are
>>>>> necessary,
>>>> The --init must be done at least once -- but don't need to do it again
>>>> until you do a --deinit.  But actually, --start will implicitly do
>>>> --init
>>>> if --init hasn't been done already.
>>>>
>>>> You only specify --no-vmlinux if you don't (or can't) specify
>>>> --vmlinux.
>>>>> can't we generate r1. modprobe oprofile
>>>>> modprobe oprofile
>>>>> opcontrol --start-daemon --vmlinux=/boot/vmlinux
>>>>> --event=PC_CHANGE:500:0:1:1
>>>> Again, be SURE you do the 'opcontrol --start', which will start the
>>>> daemon (if not already started via --start-daemon) and then signal the
>>>> kernel to start the the actual profiling activity.
>>>>
>>>> I have no idea what PC_CHANGE event is or how often or under what
>>>> conditions it may occur.  Have you tried just profiling with
>>>> CPU_CYCLES?
>>>>
>>>> -Maynard
>>>>> opcontrol --dump
>>>>> opcontrol --stop
>>>>> opcontrol --shutdown
>>>>> opreport -leport with below mentioned steps
>>>>>
>>>>> Please clarify my doubt ?
>>>>>
>>>>> Thanks and Regards,
>>>>> Santhosh B
>>>>>
>>>>> -------------------------------------------------------------------------
>>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>>>> challenge
>>>>> Build the coolest Linux based applications with Moblin SDK & win great
>>>>> prizes
>>>>> Grand prize is a trip for two to an Open Source event anywhere in the
>>>>> world
>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>>>> _______________________________________________
>>>>> oprofile-list mailing list
>>>>> opr...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/oprofile-list