Bart Smaalders wrote: >> What we would like to be able to do is something like what we have in >> userland with $HWCAP, for example: >> /kernel/crypto/aes/aes_hwcap1 >> /kernel/crypto/aes/aes_hwcap2 [VIA_C7] >> /kernel/crypto/rsa/rsa_hwcap1 >> /kernel/crypto/rsa/rsa_hwcap2 [SSE MMX CMOV SEP FPU] >> >> Would this be possible to have implemented with krtld ? Or is there a >> better/existing way to provide $HWCAP like functionality for kernel >> modules ? >> >> > > So far we've not done this aside from $PLATFORM... we should. > Solaris doesn't use this for x86; so far we've just written > the code to use different internal routines depending on > what the processor features are... > > The Sparc kernels use $PLATFORM and differing cpu modules, > but that mechanism isn't flexible enough as you note. It's > particularly problematic with multiple vendors shipping > different CPUs that each implement some of the available features.
So this sounds like you support the concept of this. Do you happen to know the best person/alias to discuss the krtld implementation needed since Rod has said it isn't the same group of people as ld.so.1 ? -- Darren J Moffat
