> As far as I know this has not happened. Such a change would also have
> to include making the use of timer interrupts (as opposed to PMU counter
> interrupts) selectable at runtime. I believe the use of timer
> interrupts for oprofile data collection is still a configuration/boot
> option. Alt
821 Avenue Jack Kilby, 06270 Villeneuve Loubet.
036 420 040 R.C.S Antibes. Capital de EUR 753.920
-Original Message-
> From: zachary6626 [mailto:zachary6...@gmail.com]
> Sent: Thursday, March 01, 2012 4:45 PM
> To: Turgis, Frederic; Dave Martin
> Cc: linaro-dev
> Subje
Wrong Dave, I meant Dave Long ;-)
OMAP Platform Business Unit - OMAP System Engineering - Platform Enablement -
System Multimedia
> Hi Dave,
>
> By the way, in
> http://lists.linaro.org/pipermail/linaro-dev/2011-September/thread.html#7560,
> we
> discussed about oprofile timer mode granularit
Hi Dave,
By the way, in
http://lists.linaro.org/pipermail/linaro-dev/2011-September/thread.html#7560,
we discussed about oprofile timer mode granularity for platforms, which had the
PMU bug that loses PMU interrupts (4430, 4460 and maybe 4470).
Was this timer granularity proposed/introduced ? I
Hi,
Never had any issue with 32K and gettimeofday() on Panda (but just starting to
use clock_gettime()). It was used to timestamp events happening every few ms or
100s of us.
I would advise as a check:
- read clock_gettime()/gettimeofday() and in parallel 32K register (map and
read physical ad
bes. Capital de EUR 753.920
-Original Message-
>From: Andy Doan [mailto:andy.d...@linaro.org]
>Sent: Friday, September 23, 2011 5:00 PM
>To: Turgis, Frederic
>Cc: Avik Sil; Mathieu Desnoyers; Alexandre Montplaisir;
>linaro-dev; Ken Werner
>Subject: Re: LTTng 2.0 pre-releas
P System Engineering - Platform Enablement
Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet.
036 420 040 R.C.S Antibes. Capital de EUR 753.920
From: David Long [mailto:dave.l...@linaro.org]
Sent: Monday, September 26, 2011 7:27 AM
To:
Hi,
>Very cool. I've added this to the wiki:
>
> https://wiki.linaro.org/Resources/HowTo/LTTng
Good idea !
I could move and reference page under
https://wiki.linaro.org/Platform/DevPlatform/Tools if people agree. Well, I may
be speaking a bit quickly as I found out
https://wiki.linaro.org/Ken
Hi,
- To my understanding, oprofile is only a statistical tool based on regular
sampling like "top" (well, I shall say /proc/stat). So it runs without
impacting much your use case. I don't think it is triggered on system
transitions. For that, I would use kernel traces or kprobes.
Still a very
> Once the interrupt issue is resolved I might suggest sampling cpu-cycles as a
> workaround to real-time sampling granularity, except that there apparently
> is an issue with reliably getting interrupts from the PMU. Does anyone know
> if this is still a problem in the A9 (I've only seen it dis
> It was a bit random across the different suites. CoreMark
> uses clock_gettime(CLOCK_REALTIME, ...) which is a wall clock
> with NTP adjustments. EEMBC uses clock() which is a lower
> resolution wall clock.
So everything was mostly wall clock based. We had not tested
CLOCK_PROCESS_CPUTIME_ID
Gall [mailto:tom.g...@linaro.org]
> Sent: Tuesday, August 30, 2011 6:03 PM
> To: Turgis, Frederic
> Cc: Clark, Rob; Linaro Dev
> Subject: Re: 11.07 oprofile on panda busted?
>
> On Tue, Aug 30, 2011 at 10:53 AM, Turgis, Frederic
> wrote:
> > Hi,
> >
> > As indicat
Hi,
As indicated by Siamashka, we are expected to operate at scheduler tick rate,
i.e. 128Hz (drivers/oprofile/timer_int.c). From your test, we have 84 ticks,
i.e. 656ms of test.
Is that correct ? I checked that also in our Android kernel and it was the same.
The only impacts we have seen in th
Hi,
What was the timer used previously for benchmarks ?
Your page focuses on accuracy while I think an important point is already the
availability/functionality of clock_gettime(CLOCK_PROCESS/THREAD_CPUTIME_ID,
...) on ARM, which measures process/thread execution time vs "wall time" for
most o
Hi, (writing from my work address as frederic.tur...@linaro.org lost password
is still not reset ;-) )
To perform some systemtap checking, I need kernel package with debug symbols,
which is available in 1003.6 version from
http://ddebs.ubuntu.com/pool/universe/l/linux-linaro-omap/
So I did some
15 matches
Mail list logo
