From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/3] ARM: shmobile: armadillo800eva: enable branch prediction on defconfig
Date: Fri, 22 Feb 2013 23:04:54 +0000 [thread overview]
Message-ID: <20130222230442.GF4737@verge.net.au> (raw)
In-Reply-To: <1351731731-8435-3-git-send-email-horms@verge.net.au>
On Thu, Feb 21, 2013 at 08:46:19PM -0800, Kuninori Morimoto wrote:
> Because defconfig disabled ARM branch prediction
> by CONFIG_CPU_BPREDICT_DISABLE,
> Armadillo800eva's Bogomips and Loop were not good performance.
> This patch enabled Arm branch prediction.
> Special thanks to Ishiyama-san
>
> Reported-by: Kiyoshi Ishiyama <kiyoshi.ishiyama.wg@renesas.com>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Thanks,
should this change also be made to ag5evm_defconfig and kota2_defconfig?
Or alternatively, should we remove those boards from upstream?
* Since the following commit added for 3.8-rc1 kota2 does not appear to boot:
- b8b499c86be58cb309964fcab5b62ac4a240a878
"ARM: 7602/1: Pass real "__machine_arch_type" variable to
setup_machine_tags() procedure"
* I have no way to test ag5evm nor am I aware of anyone who is testing
that board
> ---
> arch/arm/configs/armadillo800eva_defconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/configs/armadillo800eva_defconfig b/arch/arm/configs/armadillo800eva_defconfig
> index 891318e..dd1592b 100644
> --- a/arch/arm/configs/armadillo800eva_defconfig
> +++ b/arch/arm/configs/armadillo800eva_defconfig
> @@ -20,7 +20,6 @@ CONFIG_ARCH_R8A7740=y
> CONFIG_MACH_ARMADILLO800EVA=y
> # CONFIG_SH_TIMER_TMU is not set
> CONFIG_ARM_THUMB=y
> -CONFIG_CPU_BPREDICT_DISABLE=y
> CONFIG_CACHE_L2X0=y
> CONFIG_ARM_ERRATA_430973=y
> CONFIG_ARM_ERRATA_458693=y
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-02-22 23:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 1:02 [GIT PULL v2] Renesas ARM-based SoC defconfig for v3.8 Simon Horman
2012-11-01 1:02 ` [PATCH 1/3] ARM: shmobile: mackerel: defconfig update Simon Horman
2012-11-01 1:02 ` [PATCH 2/3] ARM: shmobile: armadillo800eva: enable L2X0 cache on defconfig Simon Horman
2013-02-22 4:46 ` [PATCH 2/3] ARM: shmobile: armadillo800eva: enable branch prediction " Kuninori Morimoto
2013-02-22 23:04 ` Simon Horman [this message]
2013-02-25 0:22 ` Kiyoshi Ishiyama
2013-02-25 0:34 ` Kuninori Morimoto
2013-03-01 9:41 ` Simon Horman
2012-11-01 1:02 ` [PATCH 3/3] ARM: shmobile: leave CONFIG_INOTIFY_USER enabled by default Simon Horman
2012-11-06 2:32 ` [GIT PULL v2] Renesas ARM-based SoC defconfig for v3.8 Simon Horman
2012-11-06 8:30 ` Arnd Bergmann
2012-11-06 14:19 ` Olof Johansson
2013-01-15 0:49 ` [GIT PULL v2] Renesas ARM-based SoC defconfig for v3.9 Simon Horman
2013-01-15 0:49 ` [PATCH 1/5] ARM: mach-shmobile: mackerel: update defconfig Simon Horman
2013-01-15 0:49 ` [PATCH 2/5] ARM: mach-shmobile: fix memory size for kota2_defconfig Simon Horman
2013-01-15 0:49 ` [PATCH 3/5] ARM: mach-shmobile: kzm9g: defconfig update Simon Horman
2013-01-15 0:49 ` [PATCH 4/5] ARM: mach-shmobile: armadillo: update defconfig Simon Horman
2013-01-15 0:49 ` [PATCH 5/5] ARM: mach-shmobile: kzm9d: " Simon Horman
2013-01-15 6:44 ` [GIT PULL v2] Renesas ARM-based SoC defconfig for v3.9 Olof Johansson
2013-01-16 4:01 ` 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=20130222230442.GF4737@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).