From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: macro@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] fast path for rdhwr emulation for TLS
Date: Fri, 7 Jul 2006 19:22:44 +0100 [thread overview]
Message-ID: <20060707182244.GA28118@linux-mips.org> (raw)
In-Reply-To: <20060708.014339.89274844.anemo@mba.ocn.ne.jp>
On Sat, Jul 08, 2006 at 01:43:39AM +0900, Atsushi Nemoto wrote:
> > > For a VIVT I-cache this can result in a TLB exception. TLB handlers are
> > > not currently prepared for being called at the exception level.
> >
> > Thanks, now I understand the problem. Are there any good solutions?
> > Only I can think now is using handle_ri_slow for such CPUs.
>
> Can we use Index_Load_Data_I to load the instruction code from icache?
> Just an idea...
In addition to what Maciej said - the format of instructions in the I-cache
is not necessarily the same as in memory. Many processor store pre-decoded
instructions in the I-cache.
Ralf
next prev parent reply other threads:[~2006-07-07 18:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 15:00 [PATCH] fast path for rdhwr emulation for TLS Atsushi Nemoto
2006-07-07 15:22 ` Maciej W. Rozycki
2006-07-07 16:12 ` Atsushi Nemoto
2006-07-07 16:43 ` Atsushi Nemoto
2006-07-07 17:04 ` Maciej W. Rozycki
2006-07-07 18:22 ` Ralf Baechle [this message]
2006-07-07 16:58 ` Maciej W. Rozycki
2006-07-08 16:12 ` Atsushi Nemoto
2006-07-10 14:40 ` Atsushi Nemoto
2006-09-14 17:28 ` Ralf Baechle
2006-09-15 3:09 ` Atsushi Nemoto
2006-07-10 14:55 ` Atsushi Nemoto
2006-07-11 2:53 ` Daniel Jacobowitz
2006-07-11 3:20 ` Atsushi Nemoto
2006-09-08 17:39 ` Nigel Stephens
2006-09-09 13:56 ` Atsushi Nemoto
2006-09-10 22:30 ` Nigel Stephens
2006-09-11 5:04 ` Atsushi Nemoto
2006-09-11 8:50 ` Atsushi Nemoto
2006-09-11 9:49 ` Thiemo Seufer
2006-09-11 14:13 ` Atsushi Nemoto
2006-09-11 15:17 ` Thiemo Seufer
2006-09-11 13:09 ` Maciej W. Rozycki
2006-09-11 14:30 ` Atsushi Nemoto
2006-09-11 17:53 ` Maciej W. Rozycki
2006-09-12 1:55 ` Atsushi Nemoto
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=20060707182244.GA28118@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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.