From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 0/2] [patch 0/2] ARM: Disable outer cache before kexec call -V2
Date: Mon, 05 Jul 2010 09:25:19 -0000 [thread overview]
Message-ID: <20100705091706.660272375@linutronix.de> (raw)
The following patch series addresses the problem, that the kexec code
does not disable the outer cache before disabling the inner cache and
jumping into the new kernel. This results in random crashes of the new
kernel.
Changes since version 1:
- added flush_all() and inv_all() functions to outer_cache_fns
so OMAP can override the disable() function easily.
- changed the implementation from inv_all() -> disable() to
flush_all() -> disable() -> inv_all() according to feedback from
Russell and Catalin.
Thanks,
tglx
next reply other threads:[~2010-07-05 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 9:25 Thomas Gleixner [this message]
2010-07-05 9:25 ` [patch 1/2] arm: Disable outer (L2) cache in kexec Thomas Gleixner
2010-07-05 10:52 ` Catalin Marinas
2010-07-05 11:13 ` Thomas Gleixner
2010-07-05 11:16 ` Catalin Marinas
2010-07-05 9:25 ` [patch 2/2] arm: Implement l2x0 cache disable functions Thomas Gleixner
2010-07-05 10:54 ` Catalin Marinas
2010-07-05 11:10 ` Thomas Gleixner
2010-07-05 11:14 ` Catalin Marinas
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=20100705091706.660272375@linutronix.de \
--to=tglx@linutronix.de \
--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).