lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 29 Mar 2014 15:38:38 +0800
From:	Jovi Zhangwei <>
To:	Andi Kleen <>
Cc:	Ingo Molnar <>,
	Steven Rostedt <>,
	LKML <>,
	Masami Hiramatsu <>,
	Greg Kroah-Hartman <>,
	Frederic Weisbecker <>
Subject: Re: [PATCH 16/28] ktap: add runtime/amalg.c


On Sat, Mar 29, 2014 at 2:52 AM, Andi Kleen <> wrote:
> Jovi Zhangwei <> writes:
>> Use amalgamation build make ktapvm.ko much smaller.
>> No amalgamation build in x86_64:
>> ktapvm.ko: 2.4M
>> amalgamation build in x86_64:
>> ktapvm.ko: 1.1M
>> User can set use amalgamation build or not in Makefile.
> This seems dubious. Is that due to debug information?
> [if yes new enough toolchain can fix that]
> If it's due to code something is seriously wrong,
> perhaps in your inlines.

Change: The kernel module size without amalgamation build is: 3.1M

I guess it's not because of debug info.

Amalgamation build is a kind of simple 'LTO', it compiles the ktapvm as
one huge C file and allows GCC to generate faster and shorter code.

But I also surprised by the size gap, will spend some time to investigate it.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists