* Compile kernel for various times and problem of too long time consuming
@ 2011-08-07 17:09 ` Amirali Shambayati
0 siblings, 0 replies; 17+ messages in thread
From: Amirali Shambayati @ 2011-08-07 17:09 UTC (permalink / raw)
To: Linux Kernel, kernelnewbies
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
Thanks for your help in advance,
--
Amirali Shambayati
Bachelor Student
Computer Engineering Department
Sharif University of Technology
Tehran, Iran
^ permalink raw reply [flat|nested] 17+ messages in thread
* Compile kernel for various times and problem of too long time consuming
2011-08-07 17:09 ` Amirali Shambayati
@ 2011-08-07 17:32 ` Amirali Shambayati
-1 siblings, 0 replies; 17+ messages in thread
From: Amirali Shambayati @ 2011-08-07 17:32 UTC (permalink / raw)
To: kernelnewbies
It is very urgent for me to find my question's answer soon.
Your help is appreciated:)
On Sun, Aug 7, 2011 at 9:39 PM, Amirali Shambayati
<amirali.shambayati@gmail.com> 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
>
>
> Thanks for your help in advance,
>
> --
> Amirali Shambayati
> Bachelor Student
> Computer Engineering Department
> Sharif University of Technology
> Tehran, Iran
>
--
Amirali Shambayati
Bachelor Student
Computer Engineering Department
Sharif University of Technology
Tehran, Iran
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Compile kernel for various times and problem of too long time consuming
@ 2011-08-07 17:32 ` Amirali Shambayati
0 siblings, 0 replies; 17+ messages in thread
From: Amirali Shambayati @ 2011-08-07 17:32 UTC (permalink / raw)
To: Linux Kernel, kernelnewbies
It is very urgent for me to find my question's answer soon.
Your help is appreciated:)
On Sun, Aug 7, 2011 at 9:39 PM, Amirali Shambayati
<amirali.shambayati@gmail.com> 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
>
>
> Thanks for your help in advance,
>
> --
> Amirali Shambayati
> Bachelor Student
> Computer Engineering Department
> Sharif University of Technology
> Tehran, Iran
>
--
Amirali Shambayati
Bachelor Student
Computer Engineering Department
Sharif University of Technology
Tehran, Iran
^ permalink raw reply [flat|nested] 17+ messages in thread
* Compile kernel for various times and problem of too long time consuming
2011-08-07 17:32 ` Amirali Shambayati
(?)
@ 2011-08-07 19:40 ` Mulyadi Santosa
-1 siblings, 0 replies; 17+ messages in thread
From: Mulyadi Santosa @ 2011-08-07 19:40 UTC (permalink / raw)
To: kernelnewbies
Hi..
On Mon, Aug 8, 2011 at 00:32, Amirali Shambayati
<amirali.shambayati@gmail.com> wrote:
> It is very urgent for me to find my question's answer soon.
> Your help is appreciated:)
touching.....
anyway, google about ccache....
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
^ permalink raw reply [flat|nested] 17+ messages in thread
* Compile kernel for various times and problem of too long time consuming
2011-08-07 17:09 ` Amirali Shambayati
@ 2011-08-07 18:04 ` Randy Dunlap
-1 siblings, 0 replies; 17+ messages in thread
From: Randy Dunlap @ 2011-08-07 18:03 UTC (permalink / raw)
To: kernelnewbies
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 ***
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Compile kernel for various times and problem of too long time consuming
@ 2011-08-07 18:04 ` Randy Dunlap
0 siblings, 0 replies; 17+ messages in thread
From: Randy Dunlap @ 2011-08-07 18:04 UTC (permalink / raw)
To: Amirali Shambayati; +Cc: Linux Kernel, kernelnewbies
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 ***
^ permalink raw reply [flat|nested] 17+ messages in thread
* Compile kernel for various times and problem of too long time consuming
2011-08-07 18:04 ` Randy Dunlap
@ 2011-08-07 19:48 ` Amirali Shambayati
-1 siblings, 0 replies; 17+ messages in thread
From: Amirali Shambayati @ 2011-08-07 19:48 UTC (permalink / raw)
To: kernelnewbies
Would you say how you rebuild kernel?
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 ***
>
--
Amirali Shambayati
Bachelor Student
Computer Engineering Department
Sharif University of Technology
Tehran, Iran
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Compile kernel for various times and problem of too long time consuming
@ 2011-08-07 19:48 ` Amirali Shambayati
0 siblings, 0 replies; 17+ messages in thread
From: Amirali Shambayati @ 2011-08-07 19:48 UTC (permalink / raw)
To: Randy Dunlap; +Cc: Linux Kernel, kernelnewbies
Would you say how you rebuild kernel?
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 ***
>
--
Amirali Shambayati
Bachelor Student
Computer Engineering Department
Sharif University of Technology
Tehran, Iran
^ permalink raw reply [flat|nested] 17+ messages in thread
* Compile kernel for various times and problem of too long time consuming
2011-08-07 19:48 ` Amirali Shambayati
@ 2011-08-07 20:00 ` Stratos Psomadakis
-1 siblings, 0 replies; 17+ messages in thread
From: Stratos Psomadakis @ 2011-08-07 19:53 UTC (permalink / raw)
To: kernelnewbies
On 08/07/2011 10:48 PM, Amirali Shambayati wrote:
> Would you say how you rebuild kernel?
>
> 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 ***
>>
just run a make at the toplevel kernel sources directory...if you change
just one file, make won't rebuild everything, just what it needs to be
rebuilt and 'relinked'...
you're rebuilding the whole kernel every time, because you're running
make-pkg clean, which I think runs make clean and cleans every object
file you've built so far...
--
Stratos Psomadakis
<psomas@gentoo.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110807/31da8f7d/attachment-0001.bin
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Compile kernel for various times and problem of too long time consuming
@ 2011-08-07 20:00 ` Stratos Psomadakis
0 siblings, 0 replies; 17+ messages in thread
From: Stratos Psomadakis @ 2011-08-07 20:00 UTC (permalink / raw)
To: Amirali Shambayati; +Cc: Linux Kernel, kernelnewbies
[-- Attachment #1: Type: text/plain, Size: 3183 bytes --]
On 08/07/2011 10:48 PM, Amirali Shambayati wrote:
> Would you say how you rebuild kernel?
>
> 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 ***
>>
just run a make at the toplevel kernel sources directory...if you change
just one file, make won't rebuild everything, just what it needs to be
rebuilt and 'relinked'...
you're rebuilding the whole kernel every time, because you're running
make-pkg clean, which I think runs make clean and cleans every object
file you've built so far...
--
Stratos Psomadakis
<psomas@gentoo.org>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Compile kernel for various times and problem of too long time consuming
2011-08-07 19:48 ` Amirali Shambayati
@ 2011-08-07 20:02 ` Randy Dunlap
-1 siblings, 0 replies; 17+ messages in thread
From: Randy Dunlap @ 2011-08-07 19:54 UTC (permalink / raw)
To: kernelnewbies
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 ***
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Compile kernel for various times and problem of too long time consuming
@ 2011-08-07 20:02 ` Randy Dunlap
0 siblings, 0 replies; 17+ messages in thread
From: Randy Dunlap @ 2011-08-07 20:02 UTC (permalink / raw)
To: Amirali Shambayati; +Cc: Linux Kernel, kernelnewbies
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 ***
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Compile kernel for various times and problem of too long time consuming
2011-08-07 17:09 ` Amirali Shambayati
` (2 preceding siblings ...)
(?)
@ 2011-08-08 9:48 ` WANG Cong
-1 siblings, 0 replies; 17+ messages in thread
From: WANG Cong @ 2011-08-08 9:48 UTC (permalink / raw)
To: linux-kernel; +Cc: kernelnewbies
On Sun, 07 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
Don't run 'make-kpkg clean', and try to use ccache,
make CC='ccache gcc'
^ permalink raw reply [flat|nested] 17+ messages in thread* Compile kernel for various times and problem of too long time consuming
2011-08-07 17:09 ` Amirali Shambayati
@ 2011-08-08 10:55 ` Javier Martinez Canillas
-1 siblings, 0 replies; 17+ messages in thread
From: Javier Martinez Canillas @ 2011-08-08 10:55 UTC (permalink / raw)
To: kernelnewbies
On Sun, Aug 7, 2011 at 7:09 PM, Amirali Shambayati
<amirali.shambayati@gmail.com> 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
>
>
> Thanks for your help in advance,
>
> --
> Amirali Shambayati
> Bachelor Student
> Computer Engineering Department
> Sharif University of Technology
> Tehran, Iran
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
Some time ago I wrote a blog entry about "Speeding up Linux kernel
compilation", hope it helps
http://martinezjavier.blogspot.com/2011/03/speeding-up-linux-kernel-compilation.html
Best regards
--
Javier Mart?nez Canillas
(+34) 682 39 81 69
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Compile kernel for various times and problem of too long time consuming
@ 2011-08-08 10:55 ` Javier Martinez Canillas
0 siblings, 0 replies; 17+ messages in thread
From: Javier Martinez Canillas @ 2011-08-08 10:55 UTC (permalink / raw)
To: Linux Kernel, kernelnewbies
On Sun, Aug 7, 2011 at 7:09 PM, Amirali Shambayati
<amirali.shambayati@gmail.com> 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
>
>
> Thanks for your help in advance,
>
> --
> Amirali Shambayati
> Bachelor Student
> Computer Engineering Department
> Sharif University of Technology
> Tehran, Iran
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
Some time ago I wrote a blog entry about "Speeding up Linux kernel
compilation", hope it helps
http://martinezjavier.blogspot.com/2011/03/speeding-up-linux-kernel-compilation.html
Best regards
--
Javier Martínez Canillas
(+34) 682 39 81 69
^ permalink raw reply [flat|nested] 17+ messages in thread
* Compile kernel for various times and problem of too long time consuming
2011-08-08 10:55 ` Javier Martinez Canillas
(?)
@ 2011-08-08 11:12 ` Prateek Sharma
-1 siblings, 0 replies; 17+ messages in thread
From: Prateek Sharma @ 2011-08-08 11:12 UTC (permalink / raw)
To: kernelnewbies
On Mon, Aug 8, 2011 at 4:25 PM, Javier Martinez Canillas <
martinez.javier@gmail.com> wrote:
> On Sun, Aug 7, 2011 at 7:09 PM, Amirali Shambayati
> <amirali.shambayati@gmail.com> 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
> >
> >
> > Thanks for your help in advance,
> >
> > --
> > Amirali Shambayati
> > Bachelor Student
> > Computer Engineering Department
> > Sharif University of Technology
> > Tehran, Iran
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
>
> Some time ago I wrote a blog entry about "Speeding up Linux kernel
> compilation", hope it helps
>
>
> http://martinezjavier.blogspot.com/2011/03/speeding-up-linux-kernel-compilation.html
>
Is allocating a big tmpfs and copying the entire kernel tree to it a good
idea?
It seems to take >4GB though.
If there was a way to quickly copy back the changes made to the disk, it
would work quite well..
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110808/9842a8cf/attachment.html
^ permalink raw reply [flat|nested] 17+ messages in thread