All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Greg Ungerer <gerg@uclinux.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH] m68k/coldfire: flush cache when creating the signal stack frame
Date: Tue, 30 Jul 2013 16:12:56 +0200	[thread overview]
Message-ID: <8366284.jmWuEafP7M@ws-stein> (raw)
In-Reply-To: <51F76027.604@uclinux.org>

Hello Greg,

On Tuesday 30 July 2013 16:41:43, Greg Ungerer wrote:
> Hi Alexander,
> 
> On 05/06/13 21:42, 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>
> 
> Sorry for the delay.
> 
> I haven't been able to actually test it, I can't get the M5475 to
> boot in copyback cache mode at the moment. I need to debug it and
> figure out why it is broken.
> 
> For now I think the best is if I push it into for-next on the
> m68knommu git tree.
> 
> (Aside it looks like the clear_cf_icache call here is a bit bogus.
> It takes cache line number args, not virtual addresses - it works
> here because clear_cf_cache invalidates the whole icache... :-(

Yep, the problem is that IIRC coldfire can only invalidate the whole cache, or single cache lines where I think it is impossible to find out which one to invalidate.

Best regards,
Alexander

      reply	other threads:[~2013-07-30 14:12 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
2013-07-30  6:41 ` Greg Ungerer
2013-07-30 14:12   ` Alexander Stein [this message]

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=8366284.jmWuEafP7M@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.