From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/03] ARM: shmobile: Use shmobile_init_delay() on r8a7791
Date: Mon, 12 May 2014 20:00:08 +0000 [thread overview]
Message-ID: <1509906.x9u0HJ6AbJ@avalon> (raw)
In-Reply-To: <20140511232508.20177.11556.sendpatchset@w520>
Hi Magnus,
On Monday 12 May 2014 08:25:08 Magnus Damm wrote:
> ARM: shmobile: Use shmobile_init_delay() on r8a7791
>
> [PATCH 01/03] ARM: shmobile: Use r8a7791 DT CPU Frequency in common case
> [PATCH 02/03] ARM: shmobile: Use r8a7791 DT CPU Frequency for Koelsch
> [PATCH 03/03] ARM: shmobile: Remove unused r8a7791_init_early()
>
> Convert r8a7791 to rely on shmobile_init_delay() instead of using a per-SoC
> delay setup function.
I'm afraid this patch set causes a boot time and CPU load regression on
Koelsch. With Simon's latest devel branch which has the patches applied, the
kernel boot time (using koelsch_defconfig) up to the point where the kernel
tries to connect to the DHCP server is 17.898437s. The CPU load (as reported
by top) on an idle system is then around 33%, spent in [kworker/0:1]. If I
revert the patches the same time goes down to 1.921875s and the CPU load on an
idle system is close to 0.
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Written against renesas-devel-v3.15-rc5-20140511
>
> arch/arm/mach-shmobile/board-koelsch-reference.c | 2 +-
> arch/arm/mach-shmobile/board-koelsch.c | 2 +-
> arch/arm/mach-shmobile/include/mach/r8a7791.h | 1 -
> arch/arm/mach-shmobile/setup-r8a7791.c | 9 +--------
> 4 files changed, 3 insertions(+), 11 deletions(-)
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/03] ARM: shmobile: Use shmobile_init_delay() on r8a7791
Date: Mon, 12 May 2014 22:00:08 +0200 [thread overview]
Message-ID: <1509906.x9u0HJ6AbJ@avalon> (raw)
In-Reply-To: <20140511232508.20177.11556.sendpatchset@w520>
Hi Magnus,
On Monday 12 May 2014 08:25:08 Magnus Damm wrote:
> ARM: shmobile: Use shmobile_init_delay() on r8a7791
>
> [PATCH 01/03] ARM: shmobile: Use r8a7791 DT CPU Frequency in common case
> [PATCH 02/03] ARM: shmobile: Use r8a7791 DT CPU Frequency for Koelsch
> [PATCH 03/03] ARM: shmobile: Remove unused r8a7791_init_early()
>
> Convert r8a7791 to rely on shmobile_init_delay() instead of using a per-SoC
> delay setup function.
I'm afraid this patch set causes a boot time and CPU load regression on
Koelsch. With Simon's latest devel branch which has the patches applied, the
kernel boot time (using koelsch_defconfig) up to the point where the kernel
tries to connect to the DHCP server is 17.898437s. The CPU load (as reported
by top) on an idle system is then around 33%, spent in [kworker/0:1]. If I
revert the patches the same time goes down to 1.921875s and the CPU load on an
idle system is close to 0.
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Written against renesas-devel-v3.15-rc5-20140511
>
> arch/arm/mach-shmobile/board-koelsch-reference.c | 2 +-
> arch/arm/mach-shmobile/board-koelsch.c | 2 +-
> arch/arm/mach-shmobile/include/mach/r8a7791.h | 1 -
> arch/arm/mach-shmobile/setup-r8a7791.c | 9 +--------
> 4 files changed, 3 insertions(+), 11 deletions(-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-05-12 20:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 23:25 [PATCH 00/03] ARM: shmobile: Use shmobile_init_delay() on r8a7791 Magnus Damm
2014-05-11 23:25 ` Magnus Damm
2014-05-11 23:25 ` [PATCH 01/03] ARM: shmobile: Use r8a7791 DT CPU Frequency in common case Magnus Damm
2014-05-11 23:25 ` Magnus Damm
2014-05-11 23:25 ` [PATCH 02/03] ARM: shmobile: Use r8a7791 DT CPU Frequency for Koelsch Magnus Damm
2014-05-11 23:25 ` Magnus Damm
2014-05-11 23:25 ` [PATCH 03/03] ARM: shmobile: Remove unused r8a7791_init_early() Magnus Damm
2014-05-11 23:25 ` Magnus Damm
2014-05-12 7:10 ` [PATCH 00/03] ARM: shmobile: Use shmobile_init_delay() on r8a7791 Simon Horman
2014-05-12 7:10 ` Simon Horman
2014-05-12 20:00 ` Laurent Pinchart [this message]
2014-05-12 20:00 ` Laurent Pinchart
2014-05-13 0:59 ` Simon Horman
2014-05-13 0:59 ` Simon Horman
2014-05-13 7:12 ` Simon Horman
2014-05-13 7:12 ` Simon Horman
2014-05-13 7:33 ` Geert Uytterhoeven
2014-05-13 7:33 ` Geert Uytterhoeven
2014-05-14 3:28 ` Simon Horman
2014-05-14 3:28 ` Simon Horman
2014-05-14 3:46 ` Magnus Damm
2014-05-14 3:46 ` Magnus Damm
2014-05-14 5:00 ` Simon Horman
2014-05-14 5:00 ` Simon Horman
2014-05-14 7:09 ` Magnus Damm
2014-05-14 7:09 ` Magnus Damm
2014-05-19 23:37 ` [PATCH 00/03] ARM: shmobile: Use shmobile_init_delay() on r8a7790 Magnus Damm
2014-05-19 23:37 ` Magnus Damm
2014-05-19 23:37 ` [PATCH 01/03] ARM: shmobile: Use r8a7790 DT CPU Frequency in common case Magnus Damm
2014-05-19 23:37 ` Magnus Damm
2014-05-19 23:37 ` [PATCH 02/03] ARM: shmobile: Use r8a7790 DT CPU Frequency for Lager Magnus Damm
2014-05-19 23:37 ` Magnus Damm
2014-05-19 23:37 ` [PATCH 03/03] ARM: shmobile: Remove unused r8a7790_init_early() Magnus Damm
2014-05-19 23:37 ` Magnus Damm
2014-05-20 7:48 ` [PATCH 00/03] ARM: shmobile: Use shmobile_init_delay() on r8a7790 Geert Uytterhoeven
2014-05-20 7:48 ` Geert Uytterhoeven
2014-05-20 23:49 ` Simon Horman
2014-05-20 23:49 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1509906.x9u0HJ6AbJ@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.