Date: Sat, 22 Nov 2008 16:08:59 -0700 From: Scott Long <scottl@samsco.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, kmacy@FreeBSD.org Subject: Re: svn commit: r185162 - in head: . sys/amd64/include sys/arm/include sys/conf sys/dev/bce sys/dev/cxgb sys/dev/cxgb/sys sys/dev/cxgb/ulp/iw_cxgb sys/dev/mxge sys/dev/nxge sys/i386/include sys/i386/in... Message-ID: <4928910B.1020403@samsco.org> In-Reply-To: <20081122221953.GO6408@deviant.kiev.zoral.com.ua> References: <200811220555.mAM5tuIJ007781@svn.freebsd.org> <20081122112949.GA6408@deviant.kiev.zoral.com.ua> <3c1674c90811221326m41e229f7p6abbc0eb473e900e@mail.gmail.com> <49288222.5060205@samsco.org> <20081122221953.GO6408@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Kostik Belousov wrote: > On Sat, Nov 22, 2008 at 03:05:22PM -0700, Scott Long wrote: >> A neat hack would be for the kernel linker to scan the text and do a >> drop-in replacement of the opcode that is appropriate for the platform. >> I can't see how a CPU_XXX definition would work because it's just a >> compile time construct, one that can be included with any kernel >> compile. > > Yes, it is possible to do that. Less drastic change is to directly > check features. I moved slow code to separate section to eliminate > unconditional jump in fast path. > Only compile-tested. > As long as it works, I think it's a step in the right direction; I'm assuming that cpu_feature is a symbol filled in at runtime and not a macro for the cpuid instruction, right? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4928910B.1020403>