mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Amirali Shambayati <amirali.shambayati@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	kernelnewbies@kernelnewbies.org
Subject: Re: Compile kernel for various times and problem of too long time consuming
Date: Sun, 7 Aug 2011 13:02:36 -0700	[thread overview]
Message-ID: <20110807130236.6ec8acb6.rdunlap@xenotime.net> (raw)
In-Reply-To: <CAC-yRPTFiU4AwtcpDNse3+eRjjprVPYng9WFbYJMf_Ebe8MGYQ@mail.gmail.com>

On Mon, 8 Aug 2011 00:18:04 +0430 Amirali Shambayati wrote:

> Would you say how you rebuild kernel?

Sure, it's just a 'make' command:

$ make -j4 ARCH=i386 O=X32 all


> On Sun, Aug 7, 2011 at 10:34 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
> > On Sun, 7 Aug 2011 21:39:12 +0430 Amirali Shambayati wrote:
> >
> >> Hi all,
> >> Since I want to evaluate performance improvements by changing just one
> >> file in kernel(noop-iosched) and compiling kernel is too much
> >> time-consuming, I want to know that if I compile kernel for more than
> >> one time, does it take similar time to first time?
> >>
> >> I use following commands. If I don't use "make-kpkg clean" for next
> >> times, does it just compile the files which have been modified or it
> >> compile whole kernel package again?
> >>
> >> make-kpkg clean
> >> fakeroot make-kpkg --initrd --append-to-version=-some-string-here
> >> kernel-image kernel-headers
> >
> > Since I never use make-kpkg, I can only tell you that when I modified
> > block/noop-iosched.c and rebuilt the kernel, here is what was rebuilt:
> >
> >  GEN     /lnx/src/NEXT/linux-next-20110805/X32/Makefile
> >  CHK     include/linux/version.h
> >  Using /lnx/src/NEXT/linux-next-20110805 as source for kernel
> >  CHK     include/generated/utsrelease.h
> >  CALL    /lnx/src/NEXT/linux-next-20110805/scripts/checksyscalls.sh
> >  CHK     include/generated/compile.h
> >  CHK     kernel/config_data.h
> >  CC      block/noop-iosched.o
> >  LD      block/built-in.o
> >  LD      vmlinux.o
> >  MODPOST vmlinux.o
> >  GEN     .version
> >  CHK     include/generated/compile.h
> >  UPD     include/generated/compile.h
> >  CC      init/version.o
> >  LD      init/built-in.o
> >  LD      .tmp_vmlinux1
> >  KSYM    .tmp_kallsyms1.S
> >  AS      .tmp_kallsyms1.o
> >  LD      .tmp_vmlinux2
> >  KSYM    .tmp_kallsyms2.S
> >  AS      .tmp_kallsyms2.o
> >  LD      vmlinux
> >  SYSMAP  System.map
> >  SYSMAP  .tmp_System.map
> >  Building modules, stage 2.
> >  VOFFSET arch/x86/boot/voffset.h
> >  CC      arch/x86/boot/version.o
> >  OBJCOPY arch/x86/boot/compressed/vmlinux.bin
> >  LZMA    arch/x86/boot/compressed/vmlinux.bin.lzma
> >  MODPOST 575 modules
> >  MKPIGGY arch/x86/boot/compressed/piggy.S
> >  AS      arch/x86/boot/compressed/piggy.o
> >  LD      arch/x86/boot/compressed/vmlinux
> >  ZOFFSET arch/x86/boot/zoffset.h
> >  OBJCOPY arch/x86/boot/vmlinux.bin
> >  AS      arch/x86/boot/header.o
> >  LD      arch/x86/boot/setup.elf
> >  OBJCOPY arch/x86/boot/setup.bin
> >  BUILD   arch/x86/boot/bzImage
> > Setup is 14972 bytes (padded to 15360 bytes).
> > System is 1287 kB
> > CRC 64ecf4d
> > Kernel: arch/x86/boot/bzImage is ready  (#18)
> >
> >
> > so it's a minimal rebuild, not a full kernel rebuild.



---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2011-08-07 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-07 17:09 Amirali Shambayati
2011-08-07 17:32 ` Amirali Shambayati
2011-08-07 18:04 ` Randy Dunlap
2011-08-07 19:48   ` Amirali Shambayati
2011-08-07 20:00     ` Stratos Psomadakis
2011-08-07 20:02     ` Randy Dunlap [this message]
2011-08-08  9:48 ` WANG Cong
2011-08-08 10:55 ` Javier Martinez Canillas

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=20110807130236.6ec8acb6.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=amirali.shambayati@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®