The reason for -fpic for module code lies in the compiler. To improve the
code we use the brasl and larl instructions for function calling and
addressing data. Unluckily these two instructions have a limited range
of +-4GB. For user space programs that means that a single shared object
may not be bigger than 4GB and that no non-fpic code is linked into
shared objects. With these two restrictions we are able to generate
much better code. There is one small problem though: kernel modules.
They get loaded into the vmalloc area which is located AFTER the main
memory. A machine with more than 4 GB of main memory therefore can't
load modules anymore because the calls and references to kernel structure
can't span the distance between vmalloc area and kernel image. To get
around this problem we compile kernel modules with -fpic and make the
modutils create plt stubs and got entries. Easy ?
>The next thing I do not understand is why -fpic has the effect of marking
>the section writeable, does it make .text writeable as well? And what for?
Because -fpic code likes to relocated absolute addresses.
blue skies,
Martin
Linux/390 Design & Development, IBM Deutschland Entwicklung GmbH
Schönaicherstr. 220, D-71032 Böblingen, Telefon: 49 - (0)7031 - 16-2247
E-Mail: schwidefsky@de.ibm.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/