From: "Gavin Lambert" <gavinl@compacsort.com>
To: 'Greg Ungerer' <gerg@snapgear.com>,
'uClinux development list' <uclinux-dev@uclinux.org>
Cc: 'Philippe De Muyter' <phdm@macqel.be>,
'Geert Uytterhoeven' <geert@linux-m68k.org>,
'Linux/m68k' <linux-m68k@lists.linux-m68k.org>
Subject: RE: [uClinux-dev] [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table
Date: Thu, 7 Apr 2011 15:13:56 +1200 [thread overview]
Message-ID: <000d01cbf4d1$d50e2f90$7f2a8eb0$@com> (raw)
In-Reply-To: <4D9D24BB.3060804@snapgear.com>
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.
next prev parent reply other threads:[~2011-04-07 3:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 20:33 [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table Geert Uytterhoeven
2011-04-06 22:05 ` [uClinux-dev] " Philippe De Muyter
[not found] ` <20110406220510.GA17350@frolo.macqel>
2011-04-07 0:53 ` Greg Ungerer
2011-04-07 2:12 ` Gavin Lambert
[not found] ` <000301cbf4c9$40339fc0$c09adf40$@com>
2011-04-07 2:43 ` Greg Ungerer
2011-04-07 3:13 ` Gavin Lambert [this message]
2011-04-07 4:14 ` Greg Ungerer
[not found] ` <4D9D3A28.9060104@snapgear.com>
2011-04-07 7:04 ` Geert Uytterhoeven
2011-04-07 8:29 ` Andreas Schwab
2011-04-07 8:35 ` Philippe De Muyter
2011-04-07 8:39 ` Andreas Schwab
2011-04-13 18:03 ` Geert Uytterhoeven
2011-04-07 1:53 ` Greg Ungerer
2011-04-13 18:16 ` Geert Uytterhoeven
2011-04-17 20:13 ` Arnd Bergmann
2011-04-19 4:32 ` Greg Ungerer
2011-04-19 8:21 ` Arnd Bergmann
2011-04-19 8:30 ` Geert Uytterhoeven
2011-04-19 8:52 ` Arnd Bergmann
2011-04-19 12:26 ` Greg Ungerer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000d01cbf4d1$d50e2f90$7f2a8eb0$@com' \
--to=gavinl@compacsort.com \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=phdm@macqel.be \
--cc=uclinux-dev@uclinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox