1. 03 8月, 2010 1 次提交
  2. 15 12月, 2009 1 次提交
  3. 24 3月, 2008 1 次提交
  4. 14 2月, 2008 1 次提交
    • M
      Linux Kernel Markers: create modpost file · b2e3e658
      Mathieu Desnoyers 提交于
      This adds some new magic in the MODPOST phase for CONFIG_MARKERS.  Analogous
      to the Module.symvers file, the build will now write a Module.markers file
      when CONFIG_MARKERS=y is set.  This file lists the name, defining module, and
      format string of each marker, separated by \t characters.  This simple text
      file can be used by offline build procedures for instrumentation code,
      analogous to how System.map and Module.symvers can be useful to have for
      kernels other than the one you are running right now.
      
      The strings are made easy to extract by having the __trace_mark macro define
      the name and format together in a single array called __mstrtab_* in the
      __markers_strings section.  This is straightforward and reliable as long as
      the marker structs are always defined by this macro.  It is an unreasonable
      amount of hairy work to extract the string pointers from the __markers section
      structs, which entails handling a relocation type for every machine under the
      sun.
      
      Mathieu :
      - Ran through checkpatch.pl
      Signed-off-by: NRoland McGrath <roland@redhat.com>
      Signed-off-by: NMathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
      Cc: David Smith <dsmith@redhat.com>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      b2e3e658
  5. 29 1月, 2008 1 次提交
    • S
      kbuild: try harder to find symbol names in modpost · 9ad21c3f
      Sam Ravnborg 提交于
      The relocation record sometimes contained an address
      which was not an exactly match for a symbol.
      
      Implment some simple logic such that if there
      is a symbol within 20 bytes of the address contained
      in the relocation record then print the name of this
      symbol.
      
      With this change modpost could find symbol names
      for the remaining .init.text symbols in my
      allyesconfig build for x86_64.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      9ad21c3f
  6. 13 10月, 2007 1 次提交
  7. 17 7月, 2007 1 次提交
  8. 22 5月, 2007 1 次提交
  9. 19 5月, 2007 1 次提交
    • A
      kbuild: make better section mismatch reports on i386, arm and mips · f892b7d4
      Atsushi Nemoto 提交于
      On i386, ARM and MIPS, warn_sec_mismatch() sometimes fails to show
      usefull symbol name.  This is because empty 'refsym' due to 0 r_addend
      value.  This patch is to adjust r_addend value, consulting with
      apply_relocate() routine in kernel code.
      
      Without this patch:
        MODPOST vmlinux
      WARNING: init/built-in.o - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xf4) and 'try_name'
      WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x18a39) and 'cache_reap'
      WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x18a6b) and 'cache_reap'
      
      With this patch:
        MODPOST vmlinux
      WARNING: mm/built-in.o - Section mismatch: reference to .init.text:set_up_list3s from .text between 'kmem_cache_create' (at offset 0x18a39) and 'cache_reap'
      WARNING: mm/built-in.o - Section mismatch: reference to .init.text:set_up_list3s from .text between 'kmem_cache_create' (at offset 0x18a6b) and 'cache_reap'
      
      Now modpost can detect "kernel_init" name (and whitelist it) and show
      "set_up_list3s" name.
      Signed-off-by: NAtsushi Nemoto <anemo@mba.ocn.ne.jp>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      f892b7d4
  10. 03 5月, 2007 1 次提交
  11. 01 7月, 2006 1 次提交
  12. 10 6月, 2006 2 次提交
  13. 22 5月, 2006 2 次提交
  14. 09 5月, 2006 1 次提交
  15. 01 5月, 2006 1 次提交
  16. 03 3月, 2006 1 次提交
  17. 19 2月, 2006 2 次提交
    • S
      kbuild: check for section mismatch during modpost stage · b39927cf
      Sam Ravnborg 提交于
      Section mismatch is identified as references to .init*
      sections from non .init sections. And likewise references
      to .exit.* sections outside .exit sections.
      
      .init.* sections are discarded after a module is initialized
      and references to .init.* sections are oops candidates.
      .exit.* sections are discarded when a module is built-in and
      thus references to .exit are also oops candidates.
      
      The checks were possible to do using 'make buildcheck' which
      called the two perl scripts: reference_discarded.pl and
      reference_init.pl. This patch just moves the same functionality
      inside modpost and the scripts are then obsoleted.
      They will though be kept for a while so users can do double
      checks - but note that some .o files are skipped by the perl scripts
      so result is not 1:1.
      All credit for the concept goes to Keith Owens who implemented
      the original perl scrips - this patch just moves it to modpost.
      
      Compared to the perl script the implmentation in modpost will be run
      for each kernel build - thus catching the error much sooner, but
      the downside is that the individual .o file are not always identified.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      b39927cf
    • S
      kbuild: use warn()/fatal() consistent in modpost · cb80514d
      Sam Ravnborg 提交于
      modpost.c provides warn() and fatal() - so use them all over the place.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      cb80514d
  18. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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!
      1da177e4