All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Matt D. Robinson" <yakker@aparity.com>
Cc: linux-kernel@vger.kernel.org, lkcd-devel@lists.sourceforge.net
Subject: Re: [PATCH] LKCD for 2.5.44 (3/8): kerntypes addition
Date: Wed, 23 Oct 2002 20:15:21 +0100	[thread overview]
Message-ID: <20021023201521.A21529@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210231051250.28800-100000@nakedeye.aparity.com>; from yakker@aparity.com on Wed, Oct 23, 2002 at 10:52:35AM -0700

On Wed, Oct 23, 2002 at 10:52:35AM -0700, Matt D. Robinson wrote:
> On Wed, 23 Oct 2002, Christoph Hellwig wrote:
> |>On Wed, Oct 23, 2002 at 02:44:04AM -0700, Matt D. Robinson wrote:
> |>> This adds kerntypes into the build so that symbols can be
> |>> extracted from a single build object in the kernel.  This
> |>> also modifies the install process (where applicable) to
> |>> copy the Kerntypes file along with the kernel and map.
> |>
> |>Why can't you directly link in init/kerntypes.o?
> 
> We wanted to keep the bloat down, even as far as the
> file size is concerned.  Some people have problems with
> making the kernel image larger than it already is.  If
> Kerntypes adds another 100K to the image, that isn't a
> good thing in the eyes of some people.

I meant using init/kerntypes.o directly instead of copying it
to Kerntypes.  But after looking more into the build process
I've now noticed that Kerntypes isn't actually linked into
vmlinux at all.  But as it's a separate file you don't need
the ifdef CONFIG_CRASH_DUMP - people not wanting on their
potentially small root filesystems just don't have to copy
it.  That would be the last ifdef on CONFIG_CRASH_DUMP, so
dump.o can now be loaded into any kernel with the patch
applied.  cool! :)


  reply	other threads:[~2002-10-23 19:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23  9:42 [ANNOUNCE] LKCD for 2.5.44 - full patch set (2002.10.23) Matt D. Robinson
2002-10-23  9:42 ` [PATCH] LKCD for 2.5.44 (1/8): dump vector Matt D. Robinson
2002-10-23  9:43 ` [PATCH] LKCD for 2.5.44 (2/8): dump notifier Matt D. Robinson
2002-10-23  9:44 ` [PATCH] LKCD for 2.5.44 (3/8): kerntypes addition Matt D. Robinson
2002-10-23 16:59   ` Christoph Hellwig
2002-10-23 17:52     ` Matt D. Robinson
2002-10-23 19:15       ` Christoph Hellwig [this message]
2002-10-23 21:10         ` Matt D. Robinson
2002-10-23  9:44 ` [PATCH] LKCD for 2.5.44 (4/8): add in use for page alloc/free Matt D. Robinson
2002-10-23  9:44 ` [PATCH] LKCD for 2.5.44 (5/8): sysrq changes for dump Matt D. Robinson
2002-10-23  9:44 ` [PATCH] LKCD for 2.5.44 (6/8): dump trace/dump calls/dump_in_progress Matt D. Robinson
2002-10-23 17:01   ` Christoph Hellwig
2002-10-23 17:40     ` Matt D. Robinson
2002-10-23  9:44 ` [PATCH] LKCD for 2.5.44 (7/8): dump configuration Matt D. Robinson
2002-10-23 17:01   ` Christoph Hellwig
2002-10-23 17:54     ` Matt D. Robinson
2002-10-23  9:45 ` [PATCH] LKCD for 2.5.44 (8/8): dump driver and build files Matt D. Robinson
2002-10-23 17:40   ` Christoph Hellwig
2002-10-24 13:56     ` Suparna Bhattacharya
2002-10-28 18:29       ` Christoph Hellwig
2002-10-25  7:30     ` Matt D. Robinson
2002-10-23 18:35   ` Stephen Hemminger
2002-10-23 19:58     ` Matt D. Robinson
2002-10-25  8:51 ` [ANNOUNCE] LKCD for 2.5.44 - full patch set (2002.10.23) Matt D. Robinson

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=20021023201521.A21529@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkcd-devel@lists.sourceforge.net \
    --cc=yakker@aparity.com \
    /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.