From: Sean MacLennan <smaclennan@pikatech.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: Problem with module_init?
Date: Tue, 31 Mar 2009 23:11:53 -0400 [thread overview]
Message-ID: <20090331231153.256d1bf4@lappy.seanm.ca> (raw)
In-Reply-To: <20090331143742.083c6cb0@lappy.seanm.ca>
8d1cf34e7ad5c7738ce20d20bd7f002f562cb8b5 is first bad commit
commit 8d1cf34e7ad5c7738ce20d20bd7f002f562cb8b5
Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Thu Mar 19 19:34:08 2009 +0000
powerpc/mm: Tweak PTE bit combination definitions
This patch tweaks the way some PTE bit combinations are defined, in
such a way that the 32 and 64-bit variant become almost identical
and that will make it easier to bring in a new common pte-* file
for the new variant of the Book3-E support.
The combination of bits defining access to kernel pages are now
clearly separated from the combination used by userspace and the
core VM. The resulting generated code should remain identical
unless I made a mistake.
Note: While at it, I removed a non-sensical statement related to
CONFIG_KGDB in ppc_mmu_32.c which could cause kernel mappings to be
user accessible when that option is enabled. Probably something
that bitrot.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
:040000 040000 c105fb9641b078f1a8a60c2a7900ca2dd088b364
e90678246962d7a455aa27ba12814c11cd9b3c22 M arch
next prev parent reply other threads:[~2009-04-01 3:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 18:37 Problem with module_init? Sean MacLennan
2009-04-01 3:11 ` Sean MacLennan [this message]
2009-04-01 11:27 ` Josh Boyer
2009-04-01 14:52 ` Sean MacLennan
2009-04-01 22:24 ` Benjamin Herrenschmidt
2009-04-02 4:08 ` Sean MacLennan
2009-04-02 4:26 ` Benjamin Herrenschmidt
2009-04-02 4:39 ` Sean MacLennan
2009-04-02 4:51 ` Sean MacLennan
2009-04-02 4:54 ` Benjamin Herrenschmidt
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=20090331231153.256d1bf4@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).