linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: srinidhi.kasagar@stericsson.com (srinidhi)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 2/2] arm: Implement l2x0 cache disable function
Date: Fri, 2 Jul 2010 16:53:21 +0530	[thread overview]
Message-ID: <1278069801.4705.298.camel@bnru03> (raw)
In-Reply-To: <AANLkTillHUsJF8brOtHh8tl9Us493GsWfpjhXXsFExY7@mail.gmail.com>


> ---------- Forwarded message ----------
> From: Thomas Gleixner <tglx@linutronix.de>
> Date: Thu, Jul 1, 2010 at 9:35 PM
> Subject: [patch 2/2] arm: Implement l2x0 cache disable function
> To: LAK <linux-arm-kernel@lists.infradead.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> 
> 
> This function is called from kexec code before the inner caches are
> disabled to prevent random crashes in the new kernel.
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Index: linux-2.6/arch/arm/mm/cache-l2x0.c
> ===================================================================
> --- linux-2.6.orig/arch/arm/mm/cache-l2x0.c
> +++ linux-2.6/arch/arm/mm/cache-l2x0.c
> @@ -206,6 +206,12 @@ static void l2x0_flush_range(unsigned lo
>        spin_unlock_irqrestore(&l2x0_lock, flags);
>  }
> 
> +static void l2x0_cache_disable(void)
> +{
> +       l2x0_inv_all();
> +       writel(0, l2x0_base + L2X0_CTRL);
> +}

I think it's a problem for PL310 controller where the access to
L2X0_CTRL is secure, accessing this in non-secure mode will fault.

Srinidhi

  parent reply	other threads:[~2010-07-02 11:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 16:05 [patch 0/2] ARM: Disable outer cache before kexec call Thomas Gleixner
2010-07-01 16:05 ` [patch 1/2] arm: Disable outer (L2) cache in kexec Thomas Gleixner
2010-07-01 16:05 ` [patch 2/2] arm: Implement l2x0 cache disable function Thomas Gleixner
     [not found]   ` <AANLkTillHUsJF8brOtHh8tl9Us493GsWfpjhXXsFExY7@mail.gmail.com>
2010-07-02 11:23     ` srinidhi [this message]
2010-07-02 11:47   ` Catalin Marinas
2010-07-02 15:29     ` Thomas Gleixner
2010-07-02 16:10       ` Catalin Marinas
2010-07-02 16:39         ` Thomas Gleixner
2010-07-02 16:51           ` Shilimkar, Santosh
2010-07-02 16:54           ` Catalin Marinas
2010-07-02 17:23             ` Russell King - ARM Linux
2010-07-03  7:01             ` Shilimkar, Santosh
2010-07-04 14:07               ` Catalin Marinas
2010-07-04 15:31                 ` Shilimkar, Santosh
2010-07-04 19:09               ` Russell King - ARM Linux
2010-07-05  9:12                 ` Catalin Marinas
2010-07-02 17:21         ` Russell King - ARM Linux
2010-07-02 16:48       ` Shilimkar, Santosh
2010-07-01 16:14 ` [patch 0/2] ARM: Disable outer cache before kexec call Catalin Marinas
2010-07-01 16:28   ` Thomas Gleixner
2010-07-01 16:35     ` Catalin Marinas
2010-07-01 16:52       ` Thomas Gleixner
2010-07-01 17:14         ` Catalin Marinas
2010-07-02 10:58         ` Tony Lindgren
2010-07-01 16:38     ` Shilimkar, Santosh
2010-07-01 16:41       ` Catalin Marinas
2010-07-01 16:44         ` Shilimkar, Santosh
2010-07-01 17:06       ` Russell King - ARM Linux
2010-07-01 17:21         ` Russell King - ARM Linux
2010-07-01 17:34           ` Catalin Marinas
2010-07-01 17:48             ` Russell King - ARM Linux
2010-07-01 20:08           ` Thomas Gleixner

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=1278069801.4705.298.camel@bnru03 \
    --to=srinidhi.kasagar@stericsson.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).