Andi Kleen píše v Čt 14. 05. 2009 v 14:58 +0200: > > To rectify the situation, I saw the following options: > > > > 1. Adjust pointers in the vDSO .altinstruction section during > > vDSO setup, and then pass it to apply_alternatives() > > 2. List the relocations with objdump and add them again to vdso.S > > using the .reloc GAS directive > > 3. Link the vDSO into the kernel with relocations, i.e. not just > > as a blob > > 4. Just move the barriers back back into the main kernel. Sorry, this doesn't work, because the function is inlined. And even if it wasn't, the vDSO must be self-contained by definition. User-space cannot simply call into kernel-space. Cheers, Petr Tesarik -- To unsubscribe from this list: send the line "unsubscribe linux-x86_64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
