From: afzal.mohd.ma@gmail.com (afzal mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: NOMMU: Setup VBAR/Hivecs for secondaries cores
Date: Tue, 19 Dec 2017 16:59:54 +0530 [thread overview]
Message-ID: <20171219112954.GA14910@afzalpc> (raw)
In-Reply-To: <1513679029-5915-1-git-send-email-vladimir.murzin@arm.com>
Hi,
On Tue, Dec 19, 2017 at 10:23:49AM +0000, Vladimir Murzin wrote:
> With switch to dynamic exception base address setting, VBAR/Hivecs
> set only for boot CPU, but secondaries stay unaware of that. That
> might lead to weird effects when trying up to bring up secondaries.
>
> Fixes: ad475117d201 ("ARM: 8649/2: nommu: remove Hivecs configuration is asm")
Sorry, it was my incompetence not seeing the secondary CPU's case.
Was the issue observed on Cortex-R ?, and was it occuring with
CONFIG_CPU_HIGH_VECTOR enabled or disabled ?
Instead of,
> diff --git a/arch/arm/include/asm/memory.h b/arch/arm/include/asm/memory.h
> +#ifndef CONFIG_MMU
> +extern unsigned long setup_vectors_base(void);
> +#else
> +static inline unsigned long setup_vectors_base(void)
> +{
> + return 0;
> +}
> +#endif
> diff --git a/arch/arm/kernel/smp.c b/arch/arm/kernel/smp.c
> + setup_vectors_base();
how about,
if (!IS_ENABLED(CONFIG_MMU))
setup_vectors_base();
That would avoid #ifdef's. Also as w/ MMU, vector base is not setup
(always Hivecs), this would make clear that setup_vectors_base() is
non-existent on MMU on.
Thanks for the fix.
afzal
next prev parent reply other threads:[~2017-12-19 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 10:23 [PATCH] ARM: NOMMU: Setup VBAR/Hivecs for secondaries cores Vladimir Murzin
2017-12-19 11:29 ` afzal mohammed [this message]
2017-12-19 14:44 ` Vladimir Murzin
2017-12-20 4:52 ` afzal mohammed
2017-12-20 9:55 ` Vladimir Murzin
2017-12-20 11:49 ` afzal mohammed
2017-12-20 12:01 ` afzal mohammed
2017-12-20 12:22 ` Vladimir Murzin
2017-12-21 4:05 ` afzal mohammed
2017-12-20 12:12 ` afzal mohammed
2017-12-20 12:22 ` Vladimir Murzin
2017-12-21 3:44 ` afzal mohammed
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=20171219112954.GA14910@afzalpc \
--to=afzal.mohd.ma@gmail.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 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).