All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: linux-mips@linux-mips.org
Subject: Re: system lockup with 2.6.29 on Cavium/Octeon
Date: Thu, 21 May 2009 07:28:02 +0100	[thread overview]
Message-ID: <20090521062802.GC1656@linux-mips.org> (raw)
In-Reply-To: <4A14E6A1.4030700@snapgear.com>

On Thu, May 21, 2009 at 03:29:05PM +1000, Greg Ungerer wrote:

> Interestingly the definition of MODULE_START is like this:
>
> #if defined(CONFIG_MODULES) && defined(KBUILD_64BIT_SYM32) && \
>         VMALLOC_START != CKSSEG
> /* Load modules into 32bit-compatible segment. */
> #define MODULE_START    CKSSEG
>
>
> If MODULE_START wasn't defined then the module_alloc() code would
> have just called vmalloc() directly - and we wouldn't be in this
> mess :-)

The reason it's done like this is that if the kernel is in CKSEG0 and
modules in CKSEG2 all address references to kernel code and variables are
just 32-bit that is they can be referenced with a much shorter instruction
sequence than for full blown 64-bit code.  This is just one of the
artefacts and I think we can just ignore it.

  Ralf

  reply	other threads:[~2009-05-21  6:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  6:12 system lockup with 2.6.29 on Cavium/Octeon Greg Ungerer
2009-05-20 14:26 ` Ralf Baechle
2009-05-21  5:29   ` Greg Ungerer
2009-05-21  6:28     ` Ralf Baechle [this message]
2009-05-21 14:50   ` Atsushi Nemoto
2009-05-22  1:19     ` Greg Ungerer
2009-05-22  9:23       ` Ralf Baechle
2009-05-22 11:53       ` Atsushi Nemoto

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=20090521062802.GC1656@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=gerg@snapgear.com \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.