* mx27 running too slow
@ 2014-04-02 22:32 Fabio Estevam
2014-04-02 22:38 ` Fabio Estevam
0 siblings, 1 reply; 6+ messages in thread
From: Fabio Estevam @ 2014-04-02 22:32 UTC (permalink / raw)
To: linux-arm-kernel
Hi Alexander,
What is the BogoMIPs value you get on mx27 running 3.14?
I am running Shawn's for-next branch and it is terribly slow on a mx27pdk:
sched_clock: 32 bits at 13MHz, resolution 75ns, wraps every 322929872820ns
CPU identified as i.MX27, silicon rev 2.1
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer
frequency.. 26.60 BogoMIPS (lpj=133000)
ARM9 running at 400MHz should give around 200 BogoMIPs.
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 6+ messages in thread
* mx27 running too slow
2014-04-02 22:32 mx27 running too slow Fabio Estevam
@ 2014-04-02 22:38 ` Fabio Estevam
2014-04-08 13:49 ` Fabio Estevam
0 siblings, 1 reply; 6+ messages in thread
From: Fabio Estevam @ 2014-04-02 22:38 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Apr 2, 2014 at 7:32 PM, Fabio Estevam <festevam@gmail.com> wrote:
> Hi Alexander,
>
> What is the BogoMIPs value you get on mx27 running 3.14?
>
> I am running Shawn's for-next branch and it is terribly slow on a mx27pdk:
>
> sched_clock: 32 bits at 13MHz, resolution 75ns, wraps every 322929872820ns
> CPU identified as i.MX27, silicon rev 2.1
> Console: colour dummy device 80x30
> Calibrating delay loop (skipped), value calculated using timer
> frequency.. 26.60 BogoMIPS (lpj=133000)
>
> ARM9 running at 400MHz should give around 200 BogoMIPs.
Nevermind. On a clean 3.14 kernel I get the expected value:
Calibrating delay loop... 199.06 BogoMIPS (lpj=995328)
So this behaviour shows up only on Shawn's branch.
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 6+ messages in thread
* mx27 running too slow
2014-04-02 22:38 ` Fabio Estevam
@ 2014-04-08 13:49 ` Fabio Estevam
2014-04-08 14:31 ` Alexander Shiyan
0 siblings, 1 reply; 6+ messages in thread
From: Fabio Estevam @ 2014-04-08 13:49 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Apr 2, 2014 at 7:38 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Wed, Apr 2, 2014 at 7:32 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi Alexander,
>>
>> What is the BogoMIPs value you get on mx27 running 3.14?
>>
>> I am running Shawn's for-next branch and it is terribly slow on a mx27pdk:
>>
>> sched_clock: 32 bits at 13MHz, resolution 75ns, wraps every 322929872820ns
>> CPU identified as i.MX27, silicon rev 2.1
>> Console: colour dummy device 80x30
>> Calibrating delay loop (skipped), value calculated using timer
>> frequency.. 26.60 BogoMIPS (lpj=133000)
>>
>> ARM9 running at 400MHz should give around 200 BogoMIPs.
>
> Nevermind. On a clean 3.14 kernel I get the expected value:
>
> Calibrating delay loop... 199.06 BogoMIPS (lpj=995328)
>
> So this behaviour shows up only on Shawn's branch.
Now I am running linux-next 20140408 and I am also getting the very
slow BogoMIPS:
Calibrating delay loop (skipped), value calculated using timer
frequency.. 26.60 BogoMIPS (lpj=133000)
Alexander,
Do you see the same on Phytec mx27 board?
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: mx27 running too slow
2014-04-08 13:49 ` Fabio Estevam
@ 2014-04-08 14:31 ` Alexander Shiyan
2014-04-08 16:22 ` Fabio Estevam
0 siblings, 1 reply; 6+ messages in thread
From: Alexander Shiyan @ 2014-04-08 14:31 UTC (permalink / raw)
To: linux-arm-kernel
Tue, 8 Apr 2014 10:49:38 -0300 ?? Fabio Estevam <festevam@gmail.com>:
> On Wed, Apr 2, 2014 at 7:38 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > On Wed, Apr 2, 2014 at 7:32 PM, Fabio Estevam <festevam@gmail.com> wrote:
> >> Hi Alexander,
> >>
> >> What is the BogoMIPs value you get on mx27 running 3.14?
> >>
> >> I am running Shawn's for-next branch and it is terribly slow on a mx27pdk:
> >>
> >> sched_clock: 32 bits at 13MHz, resolution 75ns, wraps every 322929872820ns
> >> CPU identified as i.MX27, silicon rev 2.1
> >> Console: colour dummy device 80x30
> >> Calibrating delay loop (skipped), value calculated using timer
> >> frequency.. 26.60 BogoMIPS (lpj=133000)
> >>
> >> ARM9 running at 400MHz should give around 200 BogoMIPs.
> >
> > Nevermind. On a clean 3.14 kernel I get the expected value:
> >
> > Calibrating delay loop... 199.06 BogoMIPS (lpj=995328)
> >
> > So this behaviour shows up only on Shawn's branch.
>
> Now I am running linux-next 20140408 and I am also getting the very
> slow BogoMIPS:
>
> Calibrating delay loop (skipped), value calculated using timer
> frequency.. 26.60 BogoMIPS (lpj=133000)
>
> Alexander,
>
> Do you see the same on Phytec mx27 board?
Calibrating delay loop (skipped), value calculated using timer frequency.. 29.55 BogoMIPS (lpj=147777)
Can you inspect code with "git-bisect"?
---
^ permalink raw reply [flat|nested] 6+ messages in thread
* mx27 running too slow
2014-04-08 14:31 ` Alexander Shiyan
@ 2014-04-08 16:22 ` Fabio Estevam
2014-04-08 16:27 ` Sebastian Andrzej Siewior
0 siblings, 1 reply; 6+ messages in thread
From: Fabio Estevam @ 2014-04-08 16:22 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Apr 8, 2014 at 11:31 AM, Alexander Shiyan <shc_work@mail.ru> wrote:
> Tue, 8 Apr 2014 10:49:38 -0300 ?? Fabio Estevam <festevam@gmail.com>:
>> On Wed, Apr 2, 2014 at 7:38 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> > On Wed, Apr 2, 2014 at 7:32 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> >> Hi Alexander,
>> >>
>> >> What is the BogoMIPs value you get on mx27 running 3.14?
>> >>
>> >> I am running Shawn's for-next branch and it is terribly slow on a mx27pdk:
>> >>
>> >> sched_clock: 32 bits at 13MHz, resolution 75ns, wraps every 322929872820ns
>> >> CPU identified as i.MX27, silicon rev 2.1
>> >> Console: colour dummy device 80x30
>> >> Calibrating delay loop (skipped), value calculated using timer
>> >> frequency.. 26.60 BogoMIPS (lpj=133000)
>> >>
>> >> ARM9 running at 400MHz should give around 200 BogoMIPs.
>> >
>> > Nevermind. On a clean 3.14 kernel I get the expected value:
>> >
>> > Calibrating delay loop... 199.06 BogoMIPS (lpj=995328)
>> >
>> > So this behaviour shows up only on Shawn's branch.
>>
>> Now I am running linux-next 20140408 and I am also getting the very
>> slow BogoMIPS:
>>
>> Calibrating delay loop (skipped), value calculated using timer
>> frequency.. 26.60 BogoMIPS (lpj=133000)
>>
>> Alexander,
>>
>> Do you see the same on Phytec mx27 board?
>
> Calibrating delay loop (skipped), value calculated using timer frequency.. 29.55 BogoMIPS (lpj=147777)
>
> Can you inspect code with "git-bisect"?
This is the result:
$ git bisect bad
1119c84aa3053bd415ba731ada1ecef24c8f82a2 is the first bad commit
commit 1119c84aa3053bd415ba731ada1ecef24c8f82a2
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: Wed Jan 22 12:35:44 2014 +0100
ARM: imx: enable delaytimer on the imx timer
The imx can support timer-based delays, so implement this.
Skips past jiffy calibration.
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
^ permalink raw reply [flat|nested] 6+ messages in thread
* mx27 running too slow
2014-04-08 16:22 ` Fabio Estevam
@ 2014-04-08 16:27 ` Sebastian Andrzej Siewior
0 siblings, 0 replies; 6+ messages in thread
From: Sebastian Andrzej Siewior @ 2014-04-08 16:27 UTC (permalink / raw)
To: linux-arm-kernel
On 04/08/2014 06:22 PM, Fabio Estevam wrote:
>> Calibrating delay loop (skipped), value calculated using timer frequency.. 29.55 BogoMIPS (lpj=147777)
>>
>> Can you inspect code with "git-bisect"?
>
> This is the result:
>
> $ git bisect bad
> 1119c84aa3053bd415ba731ada1ecef24c8f82a2 is the first bad commit
> commit 1119c84aa3053bd415ba731ada1ecef24c8f82a2
> Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Date: Wed Jan 22 12:35:44 2014 +0100
>
> ARM: imx: enable delaytimer on the imx timer
>
> The imx can support timer-based delays, so implement this.
> Skips past jiffy calibration.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
>
The BogoMIPS output is different and based on the timer clock. The
delay loop now check the timer instead of counting cycles / loops.
The different output is not a bug.
Sebastian
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-04-08 16:27 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-02 22:32 mx27 running too slow Fabio Estevam
2014-04-02 22:38 ` Fabio Estevam
2014-04-08 13:49 ` Fabio Estevam
2014-04-08 14:31 ` Alexander Shiyan
2014-04-08 16:22 ` Fabio Estevam
2014-04-08 16:27 ` Sebastian Andrzej Siewior
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.