RE: [uClinux-dev] [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 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


[Index of Archives]     [Video for Linux]     [Yosemite News]     [Linux S/390]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux