1. 07 Aug, 2015 1 commit
  2. 27 Aug, 2014 2 commits
    • Bertrand Jacquin's avatar
      kbuild: handle module compression while running 'make modules_install'. · beb50df3
      Bertrand Jacquin authored
      Since module-init-tools (gzip) and kmod (gzip and xz) support compressed
      modules, it could be useful to include a support for compressing modules
      right after having them installed. Doing this in kbuild instead of per
      distro can permit to make this kind of usage more generic.
      This patch add a Kconfig entry to "Enable loadable module support" menu
      and let you choose to compress using gzip (default) or xz.
      Both gzip and xz does not used any extra -[1-9] option since Andi Kleen
      and Rusty Russell prove no gain is made using them. gzip is called with -n
      argument to avoid storing original filename inside compressed file, that
      way we can save some more bytes.
      On a v3.16 kernel, 'make allmodconfig' generated 4680 modules for a
      total of 378MB (no strip, no sign, no compress), the following table
      shows observed disk space gain based on the allmodconfig .config :
             |           time                |
             | manual .ko  |       make      | size | percent
             | compression | modules_install |      | gain
        -    |             |     18.61s      | 378M |
        GZIP |   3m16s     |     3m37s       | 102M | 73.41%
        XZ   |   5m22s     |     5m39s       |  77M | 79.83%
      The gain for restricted environnement seems to be interesting while
      uncompress can be time consuming but happens only while loading a module,
      that is generally done only once.
      This is fully compatible with signed modules while the signed module is
      compressed. module-init-tools or kmod handles decompression
      and provide to other layer the uncompressed but signed payload.
      Reviewed-by: default avatarWilly Tarreau <w@1wt.eu>
      Signed-off-by: default avatarBertrand Jacquin <beber@meleeweb.net>
      Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
    • Bertrand Jacquin's avatar
      modinst: wrap long lines in order to enhance cmd_modules_install · 40e42f6a
      Bertrand Jacquin authored
      Note: shouldn't we use 'install -D $(2)/$@ $@' instead of mkdir
      and cp ?
      Reviewed-by: default avatarWilly Tarreau <w@1wt.eu>
      Signed-off-by: default avatarBertrand Jacquin <beber@meleeweb.net>
      Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
  3. 19 Jun, 2014 1 commit
  4. 06 Nov, 2012 1 commit
  5. 19 Oct, 2012 1 commit
  6. 31 Aug, 2012 1 commit
    • 이건호's avatar
      scripts/Makefile.modpost: error in finding modules from .mod files. · ef591a55
      이건호 authored
      This error may happen when the user's id or path includes .ko string.
      For example, user's id is xxx.ko and building test.ko module,
      the test.mod file lists ko name and all object files.
      /home/xxx.ko/kernel_dev/device/drivers/test_io.o ...
      Current Makefile.modpost and Makefile.modinst find and list up not
      only test.ko but also other object files.
      because all of object file's path includes .ko string.
      This is a patch to fix it.
      Signed-off-by: default avatarGunho Lee <gunho.lee@lge.com>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
  7. 14 Jan, 2009 1 commit
  8. 19 Dec, 2008 1 commit
    • Jan Beulich's avatar
      kbuild: strip generated symbols from *.ko · ad7a953c
      Jan Beulich authored
      This patch changes the way __crc_ symbols are being resolved from
      using ld to do so to using the assembler, thus allowing these symbols
      to be marked local (the linker creates then as global ones) and hence
      allow stripping (for modules) or ignoring (for vmlinux) them. While at
      this, also strip other generated symbols during module installation.
      One potentially debatable point is the handling of the flags passeed
      to gcc when translating the intermediate assembly file into an object:
      passing $(c_flags) unchanged doesn't work as gcc passes --gdwarf2 to
      gas whenever is sees any -g* option, even for -g0, and despite the
      fact that the compiler would have already produced all necessary debug
      info in the C->assembly translation phase. I took the approach of just
      filtering out all -g* options, but an alternative to such negative
      filtering might be to have a positive filter which might, in the ideal
      case allow just all the -Wa,* options to pass through.
      Signed-off-by: default avatarJan Beulich <jbeulich@novell.com>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
  9. 28 Jan, 2008 1 commit
    • Sam Ravnborg's avatar
      kbuild: fix installing external modules · 9b213118
      Sam Ravnborg authored
      Eric Sandeen <sandeen@redhat.com> reported:
        Installing external modules is supposed to put them in some path
        under /lib/modules/<version>/extra/subdir/, but this change:
        makes them go under /lib/modules/<version>/extrasubdir
       (for example, make M=fs/ext3 modules_install puts ext3.ko in
      This was the case only when specifying a trailing slash to M=..
      Fixed by removing trailing slash if present so
      we correctly match dir part of target.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      Cc: Eric Sandeen <sandeen@redhat.com>
  10. 24 Jun, 2006 1 commit
    • Theodore Ts'o's avatar
      kbuild: add option for stripping modules while installing them · ac031f26
      Theodore Ts'o authored
      Add option for stripping modules while installing them.
      This function adds support for stripping modules while they are being
      installed.  CONFIG_DEBUG_KERNEL (which will probably become more
      popular as developers use kdump) causes the size of the installed
      modules to grow by a factor of 9 or so.
      Some kernel package systems solve this problem by stripping the debug
      information from /lib/modules after running "make modules_install",
      but that may not work for people who are installing directly into
      /lib/modules --- root partitions that were sized to handle 16 megs
      worth of modules may not be quite so happy with 145 megs of modules,
      so the "make modules_install" never succeeds.
      This patch allows such users to request modules_install to strip the
      modules as they are installed.
      Signed-off-by: default avatar"Theodore Ts'o" <tytso@mit.edu>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
  11. 05 Mar, 2006 1 commit
  12. 25 Jul, 2005 1 commit
    • Sam Ravnborg's avatar
      kbuild: introduce Kbuild.include · 8ec4b4ff
      Sam Ravnborg authored
      Kbuild.include is a placeholder for definitions originally present in
      both the top-level Makefile and scripts/Makefile.build.
      There were a slight difference in the filechk definition, so the most videly
      used version was kept and usr/Makefile was adopted for this syntax.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
  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!