From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Ungerer <gerg@uclinux.org>, linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH] m68k/coldfire: flush cache when creating the signal stack frame
Date: Thu, 04 Jul 2013 07:54:51 +0200 [thread overview]
Message-ID: <1525076.03WGtcQxAz@ws-stein> (raw)
In-Reply-To: <1370432559-31711-1-git-send-email-alexander.stein@systec-electronic.com>
Any feedback on this?
On Wednesday 05 June 2013 13:42:39, Alexander Stein wrote:
> When the signal stack frame is created, it must be flushed in order to
> make sure the cache fetches the correct data.
> Without cache flush the icache might pick up old cached data from an older
> signal stack frame if the signal is raised again very fast.
> In case of copyback the data cache muist be pushed first, but is untested.
>
> Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
> ---
> arch/m68k/kernel/signal.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/m68k/kernel/signal.c b/arch/m68k/kernel/signal.c
> index 2a16df3..57fd286 100644
> --- a/arch/m68k/kernel/signal.c
> +++ b/arch/m68k/kernel/signal.c
> @@ -50,6 +50,7 @@
> #include <asm/pgtable.h>
> #include <asm/traps.h>
> #include <asm/ucontext.h>
> +#include <asm/cacheflush.h>
>
> #ifdef CONFIG_MMU
>
> @@ -181,6 +182,13 @@ static inline void push_cache (unsigned long vaddr)
> asm volatile ("movec %0,%%caar\n\t"
> "movec %1,%%cacr"
> : : "r" (vaddr + 4), "r" (temp));
> + } else {
> + /* CPU_IS_COLDFIRE */
> +#if defined(CONFIG_CACHE_COPYBACK)
> + flush_cf_dcache(0, DCACHE_MAX_ADDR);
> +#endif
> + /* Invalidate instruction cache for the pushed bytes */
> + clear_cf_icache(vaddr, vaddr + 8);
> }
> }
>
>
--
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
Am Windrad 2
08468 Heinsdorfergrund
Tel.: 03765 38600-1156
Fax: 03765 38600-4100
Email: alexander.stein@systec-electronic.com
Website: www.systec-electronic.com
Managing Director: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Chemnitz, HRB 28082
next prev parent reply other threads:[~2013-07-04 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 11:42 [PATCH] m68k/coldfire: flush cache when creating the signal stack frame Alexander Stein
2013-07-04 5:54 ` Alexander Stein [this message]
2013-07-30 6:41 ` Greg Ungerer
2013-07-30 14:12 ` Alexander Stein
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=1525076.03WGtcQxAz@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@lists.linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.