All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: Booting an Ultra sparc with 2.6
Date: Tue, 26 Oct 2004 06:48:13 +0000	[thread overview]
Message-ID: <20041025234813.62f56eba.davem@davemloft.net> (raw)
In-Reply-To: <20040913143811.GH30464@ruslug.rutgers.edu>

On Tue, 26 Oct 2004 02:28:19 -0400
mcgrof@studorgs.rutgers.edu (Luis R. Rodriguez) wrote:

> Anyone know *why* this 7.5MB limit exists?

Because we lock the kernel image into the TLB, we use
4MB TLB entries (the largest UltraSPARC currently supports)
and locking 2 entries is what we limit things to.

Use modules dude.  Also, strip all debugging information
and unnecessary symbol table entries from your kernel
as well.  "make image" helps with this, use the
arch/sparc64/boot/image file that rule creates not
the top-level vmlinux file.

  parent reply	other threads:[~2004-10-26  6:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13 14:38 Booting an Ultra sparc with 2.6 Luis R. Rodriguez
2004-09-13 17:35 ` Clemens Buchacher
2004-09-13 22:21 ` Luis R. Rodriguez
2004-09-13 22:38 ` David S. Miller
2004-09-13 22:47 ` Luis R. Rodriguez
2004-09-13 22:49 ` David S. Miller
2004-09-13 23:20 ` Luis R. Rodriguez
2004-09-13 23:32 ` David S. Miller
2004-10-26  0:32 ` Luis R. Rodriguez
2004-10-26  0:38 ` Luis R. Rodriguez
2004-10-26  0:42 ` Luis R. Rodriguez
2004-10-26  2:53 ` David S. Miller
2004-10-26  6:11 ` Luis R. Rodriguez
2004-10-26  6:16 ` Andrew Gaffney
2004-10-26  6:28 ` Luis R. Rodriguez
2004-10-26  6:32 ` Andrew Gaffney
2004-10-26  6:46 ` David S. Miller
2004-10-26  6:48 ` David S. Miller [this message]
2004-10-26  9:34 ` Luis R. Rodriguez
2004-10-26  9:50 ` Luis R. Rodriguez
2004-10-27 22:58 ` Adam Kropelin
2004-10-27 23:57 ` Luis R. Rodriguez
2004-10-28  0:33 ` David S. Miller

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=20041025234813.62f56eba.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=sparclinux@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 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.