Date: Thu, 25 May 2000 12:48:33 -0600 From: Warner Losh <imp@village.org> To: Peter Wemm <peter@netplex.com.au> Cc: arch@FreeBSD.ORG Subject: Re: Preemptive kernel on older X86 hardware Message-ID: <200005251848.MAA85904@harmony.village.org> In-Reply-To: Your message of "Thu, 25 May 2000 11:37:13 PDT." <20000525183713.B28F31CE1@overcee.netplex.com.au> References: <20000525183713.B28F31CE1@overcee.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20000525183713.B28F31CE1@overcee.netplex.com.au> Peter Wemm writes: : Digital Unix (Tru64) does this too according to their white papers. : Everything is compiled to use the generic lock calls. The generic routine : modifies the caller binary code to instead call the specific routines for : the cpu configuration or replaces the call with NOPs for uniprocessor : systems. IRIX (and now Linux/mips) will bcopy the right interrupt routine to the fixed location in memory where these things live on the MIPS cpu based on what CPU you have, even to the point of having specific versions with work arounds for specific revs of the CPU (eg a R44000 v 2.2 will get the routine that works around bugs in that chip, while a R4400 v5.0 will get a faster version since that chip has no know bugs and a R3000A will get a completely different routine, etc). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005251848.MAA85904>