From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 04/04] sh: prefetch early exception data on sh3/sh4/sh4a
Date: Fri, 27 Feb 2009 07:22:12 +0000 [thread overview]
Message-ID: <20090227072211.GE28802@linux-sh.org> (raw)
In-Reply-To: <20090223071931.12300.72669.sendpatchset@rx1.opensource.se>
On Mon, Feb 23, 2009 at 04:19:31PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@igel.co.jp>
>
> Prefetch early exception data. There is unused space in our
> exception handler cache line anyway, so this is almost free.
>
Hmm, this won't work, 'pref' doesn't exist on SH-3. The binutils opcode
table defines it as arch_sh2a_nofpu_or_sh4_nommu_nofpu_up, which excludes
SH-3. mova is ok, though.
This does show how often SH-3 gets tested though, as asm/processor_32.h
happily defines prefetch() for SH-3 when it shouldn't. I'll tidy this up
and drop in a PREF() macro.
next prev parent reply other threads:[~2009-02-27 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 7:19 [PATCH 04/04] sh: prefetch early exception data on sh3/sh4/sh4a Magnus Damm
2009-02-27 7:22 ` Paul Mundt [this message]
2009-02-27 7:53 ` Magnus Damm
2009-03-02 2:30 ` Paul Mundt
2009-03-02 2:47 ` Paul Mundt
2009-03-02 2:48 ` Magnus Damm
2009-03-02 2:55 ` Magnus Damm
2009-03-16 12:00 ` Kristoffer Ericson
2009-03-16 12:50 ` Paul Mundt
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=20090227072211.GE28802@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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