From: bryan.buckley@ti.com (Buckley, Bryan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Enable I$/D$/BrPredict based on config
Date: Thu, 3 May 2012 17:58:58 -0500 [thread overview]
Message-ID: <CAG_NtY8+W67_tbT0GGRB6eFBQGa5ht8kXU6ws7nS74g2ymtPuA@mail.gmail.com> (raw)
In-Reply-To: <yw1xbom4c1ot.fsf@unicorn.mansr.com>
On Thu, May 3, 2012 at 5:57 PM, M?ns Rullg?rd <mans@mansr.com> wrote:
> "Buckley, Bryan" <bryan.buckley@ti.com> writes:
>
>> On Thu, May 3, 2012 at 5:23 PM, M?ns Rullg?rd <mans@mansr.com> wrote:
>>>
>>> Bryan Buckley <bryan.buckley@ti.com> writes:
>>>
>>> > Currently we only disable these bits based on config. Now we will
>>> > use this config option to explicitly enable these features at this
>>> > point regardless of what bootloader, other SW, or HW did before.
>>> >
>>> > Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
>>> > ---
>>> > ?arch/arm/kernel/head.S | ? ?6 ++++++
>>> > ?1 files changed, 6 insertions(+), 0 deletions(-)
>>> >
>>> > diff --git a/arch/arm/kernel/head.S b/arch/arm/kernel/head.S
>>> > index 3bf0c7f..cec0de5 100644
>>> > --- a/arch/arm/kernel/head.S
>>> > +++ b/arch/arm/kernel/head.S
>>> > @@ -411,12 +411,18 @@ __enable_mmu:
>>> > ?#endif
>>> > ?#ifdef CONFIG_CPU_DCACHE_DISABLE
>>> > ? ? ? bic ? ? r0, r0, #CR_C
>>> > +#else
>>> > + ? ? orr ? ? r0, r0, #CR_C
>>> > ?#endif
>>> > ?#ifdef CONFIG_CPU_BPREDICT_DISABLE
>>> > ? ? ? bic ? ? r0, r0, #CR_Z
>>> > +#else
>>> > + ? ? orr ? ? r0, r0, #CR_Z
>>> > ?#endif
>>> > ?#ifdef CONFIG_CPU_ICACHE_DISABLE
>>> > ? ? ? bic ? ? r0, r0, #CR_I
>>> > +#else
>>> > + ? ? orr ? ? r0, r0, #CR_I
>>> > ?#endif
>>> > ?#ifdef CONFIG_ARM_LPAE
>>> > ? ? ? mov ? ? r5, #0
>>> > --
>>>
>>> Caches and branch predictors may require implementation defined
>>> invalidation before being enabled.
>>
>> True.. I was relying on going through arch/arm/boot/compressed/head.S
>> to do that for me. Was that unreasonable?
>
> I'd be inclined to qualify that as "other SW." ?It is possible to start
> the kernel without using that code, even if it is not typically done.
>
haha, yeah me too.
Thanks M?ns and Russel.
> --
> M?ns Rullg?rd
> mans at mansr.com
next prev parent reply other threads:[~2012-05-03 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 21:00 [PATCH] ARM: Enable I$/D$/BrPredict based on config Bryan Buckley
2012-05-03 22:23 ` Måns Rullgård
2012-05-03 22:48 ` Buckley, Bryan
2012-05-03 22:52 ` Russell King - ARM Linux
2012-05-03 22:57 ` Måns Rullgård
2012-05-03 22:58 ` Buckley, Bryan [this message]
2012-05-03 22:51 ` Russell King - ARM Linux
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=CAG_NtY8+W67_tbT0GGRB6eFBQGa5ht8kXU6ws7nS74g2ymtPuA@mail.gmail.com \
--to=bryan.buckley@ti.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).