-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hannes Reinecke wrote:
Jeff Mahoney wrote:
I'm still not a fan of this, but in the absence of the ability to link in modules at install time, I guess the gains outweigh the drawbacks.
Why don't we do something about it?
I've already spent some thoughts about it, and come up with two possibilities:
- Link in modules during initrd run. Shouldn't be too hard, after all that's what the kernel does nowadays during building anyway. So just some linker magic and you're done. Drawback is that you'd need an uncompressed kernel to start with, so I'm not sure it's the right way to go
This is something we discussed briefly a few months ago and the consensus was that there just wasn't enough information in the installation to properly link and assemble the new image. The idea just sort of petered out. I was thinking, though, that with the addition of a few more files, we might be able to make it work. The helpers in .../tools/, setup.bin, and a bit of scripting might be enough, but I haven't looked into it deeply enough to back that up with solid data.
- Implement something like the 'kexec-cache' from Max OS-X. OS-X has a 'kexec-cache', which allow to preload some kernel modules during boot. Implementing a similar thing on Linux we could just stuff the preloaded modules into a blob and load this as an additional initrd image. Then we could just call the ->init calls and everything would be dandy. Or that's the hope.
Wouldn't this also require a build environment? If not, doesn't it run into the same problem that we have now with serially loading the modules? - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAko/mVIACgkQLPWxlyuTD7K0qQCgj6V9ry7ZgIHNuanefpwqD6uR Vv0AoKSPOMjfmT95ikkCIA6D79W2BvvL =NMkp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org