1. 19 Dec, 2008 1 commit
    • Jan Beulich's avatar
      allow stripping of generated symbols under CONFIG_KALLSYMS_ALL · 9bb48247
      Jan Beulich authored
      Building upon parts of the module stripping patch, this patch
      introduces similar stripping for vmlinux when CONFIG_KALLSYMS_ALL=y.
      Using CONFIG_KALLSYMS_STRIP_GENERATED reduces the overhead of
      CONFIG_KALLSYMS_ALL from 245k/310k to 65k/80k for the (i386/x86-64)
      kernels I tested with.
      The patch also does away with the need to special case the kallsyms-
      internal symbols by making them available even in the first linking
      While it is a generated file, the patch includes the changes to
      scripts/genksyms/keywords.c_shipped, as I'm unsure what the procedure
      here is.
      Signed-off-by: default avatarJan Beulich <jbeulich@novell.com>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
  2. 19 May, 2008 1 commit
    • Sam Ravnborg's avatar
      kbuild: filter away debug symbols from kernel symbols · aab34ac8
      Sam Ravnborg authored
      Andi Kleen <andi@firstfloor.org>
      reported that he saw a lot of symbols like this:
      0000000000000b24 N DW.aio.h.903a6d92.2
      0000000000000bce N DW.task_io_accounting.h.8d8de327.0
      0000000000000bec N DW.hrtimer.h.c23659c6.0
      in his System.map / kallsyms output.
      Simple solution is to skip all debugging
      symbols (they are marked 'N').
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      Cc: Paulo Marques <pmarques@grupopie.com>
  3. 30 Apr, 2008 1 commit
  4. 06 Feb, 2008 2 commits
  5. 17 Jul, 2007 2 commits
  6. 08 Dec, 2006 1 commit
  7. 06 Dec, 2006 2 commits
  8. 25 Mar, 2006 1 commit
  9. 07 Sep, 2005 2 commits
  10. 27 Jul, 2005 1 commit
  11. 05 May, 2005 1 commit
  12. 01 May, 2005 1 commit
  13. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      Let it rip!