Date: Fri, 5 Jul 2002 21:25:30 -0400 From: Jake Burkholder <jake@locore.ca> To: Julian Elischer <julian@elischer.org> Cc: Peter Wemm <peter@wemm.org>, FreeBSD current users <current@FreeBSD.ORG> Subject: Re: i386 trap code Message-ID: <20020705212530.C839@locore.ca> In-Reply-To: <Pine.BSF.4.21.0207051736540.14813-100000@InterJet.elischer.org>; from julian@elischer.org on Fri, Jul 05, 2002 at 05:43:26PM -0700 References: <Pine.BSF.4.21.0207051736540.14813-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Apparently, On Fri, Jul 05, 2002 at 05:43:26PM -0700, Julian Elischer said words to the effect of; > > Looking at i386/exception.s > one sees: [...] > > Now: > > would it not make a lot of sense to put doreti immediatly after > calltrap: in the same file > so that one could follow the entire picture without having to bounce back > and forth between two files? I'd say so, yeah. Its probably there because it used to be alongside splz and unmasked pending isa interrupts. > > (also gets rid of the jmp in the common case) System calls are probably the common case. But I'd suggest just put it after the trap code at the end of the file and leave the jump. Its super aligned so there would probably be a bunch of nops to plow through anyway. Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020705212530.C839>