From: Thiemo Seufer <ths@networkno.de>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: nigel@mips.com, ralf@linux-mips.org, dan@debian.org,
macro@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] fast path for rdhwr emulation for TLS
Date: Mon, 11 Sep 2006 16:17:34 +0100 [thread overview]
Message-ID: <20060911151734.GC13414@networkno.de> (raw)
In-Reply-To: <20060911.231314.25910522.anemo@mba.ocn.ne.jp>
Atsushi Nemoto wrote:
> On Mon, 11 Sep 2006 10:49:05 +0100, Thiemo Seufer <ths@networkno.de> wrote:
> > > + tlbp
> >
> > This needs a .set mips3/.set mips0 pair.
>
> The TLBP is belong to MIPS I ISA, isn't it?
Uh, right. I wasn't awake when I wrote that mail. :-)
> > > +#ifdef CONFIG_CPU_MIPSR2
> > > + _ehb /* tlb_probe_hazard */
> > > +#else
> > > + nop; nop; nop; nop; nop; nop /* tlb_probe_hazard */
> > > +#endif
> >
> > What about a mtc0_tlbp_hazard macro here?
>
> You mean mtc0_tlbw_hazard? I took them from tlb_probe_hazard macro in
> queue branch.
Actually, I meant an equivalent to the build_tlb_probe_entry in tlbex.c,
plus a tlb_use_hazard.
> And it looks current mtc0_tlbw_hazard asm macro does not match with
> its C equivalent ...
>
> .macro mtc0_tlbw_hazard
> b . + 8
> .endm
>
> #define mtc0_tlbw_hazard() \
> __asm__ __volatile__( \
> " .set noreorder \n" \
> " nop \n" \
> " nop \n" \
> " nop \n" \
> " nop \n" \
> " nop \n" \
> " nop \n" \
> " .set reorder \n")
It also lacks a case for R2 CPUs, where IIRC _ehb is the the way
approved by the spec.
Thiemo
next prev parent reply other threads:[~2006-09-11 15:19 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
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 [this message]
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=20060911151734.GC13414@networkno.de \
--to=ths@networkno.de \
--cc=anemo@mba.ocn.ne.jp \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=nigel@mips.com \
--cc=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox