From: Brian Gerst <bgerst@didntduck.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: christoph <christoph@scalex86.org>,
Christoph Hellwig <hch@infradead.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Move some more structures into "mostly_readonly"
Date: Tue, 07 Jun 2005 17:31:19 -0400 [thread overview]
Message-ID: <42A61227.9090402@didntduck.org> (raw)
In-Reply-To: <1118177949.5497.44.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Tue, 2005-06-07 at 12:59 -0700, christoph wrote:
>
>>On Tue, 7 Jun 2005, Christoph Hellwig wrote:
>>
>>
>>>On Tue, Jun 07, 2005 at 11:30:03AM -0700, christoph wrote:
>>>
>>>>Move syscall table, timer_hpet and the boot_cpu_data into the "mostly_readonly" section.
>>>
>>>the syscall table should be completely readonly.
>>
>>Why was it in .data in the first place? There must be some reason why it
>>was writable?
>
>
> probably a historic oversight.
>
It doesn't really matter. .rodata isn't actually mapped read-only.
Doing so would break up the large pages used to map the kernel.
--
Brian Gerst
next prev parent reply other threads:[~2005-06-07 21:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 18:30 [PATCH] Move some more structures into "mostly_readonly" christoph
2005-06-07 19:41 ` Christoph Hellwig
2005-06-07 19:59 ` christoph
2005-06-07 20:59 ` Arjan van de Ven
2005-06-07 21:31 ` Brian Gerst [this message]
2005-06-07 22:23 ` christoph
2005-06-07 22:54 ` Jeremy Maitin-Shepard
2005-06-08 6:29 ` Arjan van de Ven
2005-06-08 17:56 ` Jeremy Maitin-Shepard
2005-06-08 10:00 ` Jörn Engel
2005-06-08 10:07 ` Arjan van de Ven
2005-06-08 10:20 ` Jörn Engel
2005-06-08 10:35 ` Arjan van de Ven
2005-06-08 11:08 ` Jörn Engel
2005-06-08 14:24 ` Arnd Bergmann
2005-06-08 12:16 ` Pavel Machek
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=42A61227.9090402@didntduck.org \
--to=bgerst@didntduck.org \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=christoph@scalex86.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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