nel.org
> Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement
>
> Hi Vishwa,
>
> On Mon, Sep 6, 2010 at 1:15 PM, Sripathy, Vishwanath
> wrote:
> > I did some profiling of assembly code on OMAP3630 board (ZOOM3). In worst
> > case
> it takes around 3.28ms a
Hi Vishwa,
On Mon, Sep 6, 2010 at 1:15 PM, Sripathy, Vishwanath
wrote:
> I did some profiling of assembly code on OMAP3630 board (ZOOM3). In worst
> case it takes around 3.28ms and best case around 2.93ms for mpu off mode.
Can you give a bit more details? Which measurement has been taken (ASM
on
ro.org; linux-
> o...@vger.kernel.org
> Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement
>
> Hi Amit, Santosh,
>
> On Thu, Sep 2, 2010 at 10:11 AM, Shilimkar, Santosh
> wrote:
> ...
> >> > The point is to keep the minimum possible in the kernel: just
Amit Kucheria writes:
> On 10 Aug 27, Kevin Hilman wrote:
>> vishwanath.sripa...@linaro.org writes:
>>
>> > From: Vishwanath BS
>> >
>> > This patch has instrumentation code for measuring latencies for
>> > various CPUIdle C states for OMAP. Idea here is to capture the
>> > timestamp at various
Hi Amit, Santosh,
On Thu, Sep 2, 2010 at 10:11 AM, Shilimkar, Santosh
wrote:
...
>> > The point is to keep the minimum possible in the kernel: just the
>> > tracepoints we're interested in. The rest (calculations, averages,
>> > analysis, etc.) does not need to be in the kernel and can be done
; Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement
>
> On 10 Aug 27, Kevin Hilman wrote:
> > vishwanath.sripa...@linaro.org writes:
> >
> > > From: Vishwanath BS
> > >
> > > This patch has instrumentation code for measuring latencies for
&g
On 10 Aug 27, Kevin Hilman wrote:
> vishwanath.sripa...@linaro.org writes:
>
> > From: Vishwanath BS
> >
> > This patch has instrumentation code for measuring latencies for
> > various CPUIdle C states for OMAP. Idea here is to capture the
> > timestamp at various phases of CPU Idle and then comp
-...@lists.linaro.org
> Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement
>
> On Tue, Aug 31, 2010 at 10:28 AM, Sripathy, Vishwanath
> wrote:
> >
> >
> >> -Original Message-
> >> From: Silesh C V [mailto:sailes...@gmail.com]
> >&
naro.org; linux-omap@vger.kernel.org;
>> linaro-...@lists.linaro.org
>> Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement
>>
>> Hi Vishwa,
>>
>> On Mon, Aug 30, 2010 at 6:29 PM, Sripathy, Vishwanath
>> wrote:
>> > Kevin,
>> >
t;> ow...@vger.kernel.org] On Behalf Of Kevin Hilman
> >> Sent: Saturday, August 28, 2010 12:45 AM
> >> To: vishwanath.sripa...@linaro.org
> >> Cc: linux-omap@vger.kernel.org; linaro-...@lists.linaro.org
> >> Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency m
:45 AM
>> To: vishwanath.sripa...@linaro.org
>> Cc: linux-omap@vger.kernel.org; linaro-...@lists.linaro.org
>> Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement
>>
>> vishwanath.sripa...@linaro.org writes:
>>
>> > From: Vishwanath BS
.@lists.linaro.org
> Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement
>
> vishwanath.sripa...@linaro.org writes:
>
> > From: Vishwanath BS
> >
> > This patch has instrumentation code for measuring latencies for
> > various CPUIdle C states for OMAP
Amit Kucheria writes:
> On 10 Aug 28, vishwanath.sripa...@linaro.org wrote:
>> From: Vishwanath BS
>>
>> This patch has instrumentation code for measuring latencies for
>> various CPUIdle C states for OMAP. Idea here is to capture the
>> timestamp at various phases of CPU Idle and then compute
On 10 Aug 28, vishwanath.sripa...@linaro.org wrote:
> From: Vishwanath BS
>
> This patch has instrumentation code for measuring latencies for
> various CPUIdle C states for OMAP. Idea here is to capture the
> timestamp at various phases of CPU Idle and then compute the sw
> latency for various c
vishwanath.sripa...@linaro.org writes:
> From: Vishwanath BS
>
> This patch has instrumentation code for measuring latencies for
> various CPUIdle C states for OMAP. Idea here is to capture the
> timestamp at various phases of CPU Idle and then compute the sw
> latency for various c states. For
kernel.org; linaro-...@lists.linaro.org; Jean Pihet;
> Chalhoub, Nicole; Bour, Vincent
> Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement
>
> Hi Vishwa,
>
> On 8/28/2010 12:08 AM, vishwanath.sripa...@linaro.org wrote:
> > From: Vishwanath BS
> >
>
Benoit,
On Fri, Aug 27, 2010 at 12:25 PM, Cousson, Benoit wrote:
>> This patch has instrumentation code for measuring latencies for
>> various CPUIdle C states for OMAP. Idea here is to capture the
>> timestamp at various phases of CPU Idle and then compute the sw
>> latency for various c states.
Hi Vishwa,
On 8/28/2010 12:08 AM, vishwanath.sripa...@linaro.org wrote:
From: Vishwanath BS
This patch has instrumentation code for measuring latencies for
various CPUIdle C states for OMAP. Idea here is to capture the
timestamp at various phases of CPU Idle and then compute the sw
latency for
.org
> Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement
>
> g 28, 2010 at 3:38 AM, wrote:
> > From: Vishwanath BS
> >
> > This patch has instrumentation code for measuring latencies for
> > various CPUIdle C states for OMAP. Idea here is to capture
.org
> Subject: Re: [PATCH] OMAP CPUIDLE: CPU Idle latency measurement
>
> Hi,
>
> On Sat, Aug 28, 2010 at 12:08 AM, wrote:
> > From: Vishwanath BS
> >
> > This patch has instrumentation code for measuring latencies for
> > various CPUIdle C states for OMAP. Id
g 28, 2010 at 3:38 AM, wrote:
> From: Vishwanath BS
>
> This patch has instrumentation code for measuring latencies for
> various CPUIdle C states for OMAP. Idea here is to capture the
> timestamp at various phases of CPU Idle and then compute the sw
> latency for various c states. For OMAP, 32k
Hi,
On Sat, Aug 28, 2010 at 12:08 AM, wrote:
> From: Vishwanath BS
>
> This patch has instrumentation code for measuring latencies for
> various CPUIdle C states for OMAP. Idea here is to capture the
> timestamp at various phases of CPU Idle and then compute the sw
> latency for various c state
From: Vishwanath BS
This patch has instrumentation code for measuring latencies for
various CPUIdle C states for OMAP. Idea here is to capture the
timestamp at various phases of CPU Idle and then compute the sw
latency for various c states. For OMAP, 32k clock is chosen as
reference clock this as
23 matches
Mail list logo
