Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Nigel Stephens <nigel@mips.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: 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: Sun, 10 Sep 2006 23:30:18 +0100	[thread overview]
Message-ID: <450491FA.3010600@mips.com> (raw)
In-Reply-To: <20060909.225641.41198763.anemo@mba.ocn.ne.jp>

Atsushi Nemoto wrote:
> On Fri, 08 Sep 2006 18:39:08 +0100, Nigel Stephens <nigel@mips.com> wrote:
>   
>>> I asked on GCC bugzilla a few days ago but can not got feedback yet.
>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28126
>>>   
>>>       
>> In spite of the GCC issue, is this patch now at the point where it could
>> be applied, or at least queued?
>>     
>
> GCC 4.2 does not put RDHWR in delay slot now.  Also, there is a
> "hackish fix" to prevent gcc move a RDHWR outside of a conditional
> (from Richard Sandiford).
>
> For kernel side, my patch can be still applied to current git tree as
> is.
>
> But I'm still looking for better solution (silver bullet?) for
> cpu_has_vtag_icache case.
>
> How about something like this (and do not touch tlbex.c)?
>
> 	LEAF(handle_ri_rdhwr_vivt)
> 	.set	push
> 	.set	noat
> 	.set	noreorder
> 	/* check if TLB contains a entry for EPC */
> 	MFC0	K1, CP0_ENTRYHI
> 	andi	k1, ASID_MASK
> 	MFC0	k0, CP0_EPC
> 	andi	k0, PAGE_MASK << 1
> 	or	k1, k0
> 	MTC0	k1, CP0_ENTRYHI
> 	tlbp
> 	mfc0	k1, CP0_INDEX
> 	bltz	k1, handle_ri	/* slow path */
> 	 nop
> 	/* fall thru */
> 	LEAF(handle_ri_rdhwr)
>
> I'm wondering if this could work on CONFIG_MIPS_MT_SMTC case...
>
>   

No, that wouldn't be reliable for CONFIG_MIPS_MT_SMTC, but then again 
the only CPU which currently runs SMTC has VIPT caches

Nigel

  reply	other threads:[~2006-09-10 22:30 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 [this message]
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=450491FA.3010600@mips.com \
    --to=nigel@mips.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=dan@debian.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --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