From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Wed, 24 Nov 2004 09:46:31 +0000 (GMT) Received: from pD9562327.dip.t-dialin.net ([IPv6:::ffff:217.86.35.39]:16164 "EHLO mail.linux-mips.net") by linux-mips.org with ESMTP id ; Wed, 24 Nov 2004 09:46:26 +0000 Received: from fluff.linux-mips.net (localhost [127.0.0.1]) by mail.linux-mips.net (8.13.1/8.13.1) with ESMTP id iAO9iN5W021636; Wed, 24 Nov 2004 10:44:23 +0100 Received: (from ralf@localhost) by fluff.linux-mips.net (8.13.1/8.13.1/Submit) id iAO9iNMa021635; Wed, 24 Nov 2004 10:44:23 +0100 Date: Wed, 24 Nov 2004 10:44:23 +0100 From: Ralf Baechle To: Thiemo Seufer Cc: "Maciej W. Rozycki" , Manish Lachwani , Geert Uytterhoeven , Linux/MIPS Development Subject: Re: [PATCH] Synthesize TLB refill handler at runtime Message-ID: <20041124094423.GB21039@linux-mips.org> References: <20041121170242.GR20986@rembrandt.csv.ica.uni-stuttgart.de> <20041121203757.GS20986@rembrandt.csv.ica.uni-stuttgart.de> <20041122070117.GB25433@linux-mips.org> <41A283BD.3080300@mvista.com> <41A29DCF.8030308@mvista.com> <20041124014057.GE902@rembrandt.csv.ica.uni-stuttgart.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041124014057.GE902@rembrandt.csv.ica.uni-stuttgart.de> User-Agent: Mutt/1.4.1i Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 6432 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: ralf@linux-mips.org Precedence: bulk X-list: linux-mips On Wed, Nov 24, 2004 at 02:40:57AM +0100, Thiemo Seufer wrote: > > default: > > /* > > * Others are assumed to have one cycle mtc0 hazard, > > - * and one cycle tlbwr hazard. > > + * and one cycle tlbwr hazard or to understand ehb. > > * XXX: This might be overly general. > > */ > > - i_nop(p); > > + i_ehb(p); > > i_tlbwr(p); > > - i_nop(p); > > + i_ehb(p); > > break; > > Does r24k really need both delays? If not, it should get its own case. > Probably it should be separated even if it is identical, the code above > is nothing but a guess based on preexisting code. I would suggest to default to EHB only for architecture revision 2. For any pre-V2 processor the outcome of a default case is basically luck and so I would suggest to just panic and force people to read their CPU manual. Ralf