From: Johannes Stezenbach <js@convergence.de>
To: Richard Hodges <rh@matriplex.com>
Cc: "Kevin D. Kissell" <kevink@mips.com>, linux-mips@oss.sgi.com
Subject: Re: LL/SC benchmarking [was: Mipsel libc with LL/SC online anywhere?]
Date: Mon, 22 Jul 2002 12:35:35 +0200 [thread overview]
Message-ID: <20020722103534.GA16198@convergence.de> (raw)
In-Reply-To: <Pine.BSF.4.10.10207190846180.1937-100000@mail.matriplex.com>
On Fri, Jul 19, 2002 at 08:54:46AM -0700, Richard Hodges wrote:
> On Fri, 19 Jul 2002, Johannes Stezenbach wrote:
>
> > I think the beql-hack needs a kernel patch to guarantee k1 !=
> > MAGIC_COOKIE after each eret, but for a those few tests I was just
> > taking my chance.
>
> Maybe something like this in front of every "eret" instruction?
>
> #ifdef CONFIG_CPU_VR41XX
> move $27,$0
> #endif
The Sony patch for CPUs without LL/SC and without branch-likely
(posted here on Tue 22 Jan 2002 15:27:44 +0900 by
Machida Hiroyuki <machida@sm.sony.co.jp>) requires to load
a certain magic cookie into k1 before every eret/rfe.
OTOH, Kevin D. Kissel speculates that for the branch-likely
trick it might be possible to find a magic value that already can
never end up in k1 after an eret, as side effect of the
current implementation. So we wouldn't have to patch the
kernel at all.
I for one would be content if I could find a magic cookie value
that lets me avoid adding instructions to the TLB refill handler.
Johannes
next prev parent reply other threads:[~2002-07-22 10:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 13:04 Mipsel libc with LL/SC online anywhere? Kevin D. Kissell
2002-07-12 13:04 ` Kevin D. Kissell
2002-07-19 12:38 ` LL/SC benchmarking [was: Mipsel libc with LL/SC online anywhere?] Johannes Stezenbach
2002-07-19 15:54 ` Richard Hodges
2002-07-22 10:35 ` Johannes Stezenbach [this message]
2002-07-25 16:25 ` Johannes Stezenbach
2002-07-25 17:06 ` Jun Sun
2002-07-25 18:45 ` Johannes Stezenbach
2002-07-25 18:56 ` Jun Sun
2002-07-25 19:24 ` Johannes Stezenbach
2002-07-25 21:49 ` Kevin D. Kissell
2002-07-26 19:35 ` Kevin D. Kissell
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=20020722103534.GA16198@convergence.de \
--to=js@convergence.de \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=rh@matriplex.com \
/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