On Thu, Apr 7, 2011 at 06:14, Greg Ungerer <gerg@xxxxxxxxxxxx> wrote:
On 07/04/11 13:13, Gavin Lambert wrote:
Quoth Greg Ungerer:
Doesn't that have XIP consequences? Â.text (and presumably .rodata)
can be stored and executed from ROM, since they can't be changed at
runtime. Â.data has to be in RAM, since it can be.
Yes, but even in the kernel XIP case the very early startup code
moves the kernels data to RAM. Well before the system call table
will be needed.
But presumably if the syscall table was previously in .text, it was not
subject to this. ÂAnd now it will be.
I doubt this would actually break anything (as you've already confirmed),
since it's only a tiny RAM usage increase, but unless there's some reason
for the syscall table to be read-write it seems a bit odd.
To be read-write yes, odd, but a data table being in the .text
Isn't there a reason it was read-write on m68k, like the table may be changed
at runtime (to install rootkits :-)? Have to check what the other arches do...
Gr{oetje,eeting}s,
            Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
             Â Â -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
