Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: tsbogend@alpha.franken.de, linux-mips@linux-mips.org
Subject: Re: [PATCH] IP28: added cache barrier to assembly routines
Date: Wed, 28 Nov 2007 14:48:14 +0000	[thread overview]
Message-ID: <20071128144814.GA29715@linux-mips.org> (raw)
In-Reply-To: <20071128.234142.106261815.anemo@mba.ocn.ne.jp>

On Wed, Nov 28, 2007 at 11:41:42PM +0900, Atsushi Nemoto wrote:

> On Sun, 25 Nov 2007 11:47:56 +0100, Thomas Bogendoerfer <tsbogend@alpha.franken.de> wrote:
> > IP28 needs special treatment to avoid speculative accesses. gcc
> > takes care for .c code, but for assembly code we need to do it
> > manually.
> > 
> > This is taken from Peter Fuersts IP28 patches.
> > 
> > Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> > ---
> >  arch/mips/lib/memcpy.S       |   10 ++++++++++
> >  arch/mips/lib/memset.S       |    5 +++++
> >  arch/mips/lib/strncpy_user.S |    1 +
> >  include/asm-mips/asm.h       |    8 ++++++++
> >  4 files changed, 24 insertions(+), 0 deletions(-)
> 
> I do not know details of this patch at all, but in general,
> memcpy-inatomic.S and csum_pertial.S are candidates if you changed
> memcpy.S.

tlbex.c may also need modifications.

  Ralf

      reply	other threads:[~2007-11-28 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-25 10:47 [PATCH] IP28: added cache barrier to assembly routines Thomas Bogendoerfer
2007-11-28  9:53 ` Ralf Baechle
2007-11-28 14:41 ` Atsushi Nemoto
2007-11-28 14:48   ` Ralf Baechle [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=20071128144814.GA29715@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=tsbogend@alpha.franken.de \
    /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