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:	Tue, 7 Oct 2014 15:49:12 +0200
From:	Borislav Petkov <>
To:	Arnaldo Carvalho de Melo <>
Cc:	Jean Pihet <>,
	"" <>,
	Fu Wei <>, Robert Richter <>,
	Jiri Olsa <>, David Ahern <>,
	Ingo Molnar <>,
	Thomas Gleixner <>,
	Matt Fleming <>
Subject: Re: perf & rasd integration plan

On Tue, Oct 07, 2014 at 10:40:21AM -0300, Arnaldo Carvalho de Melo wrote:
> Right, we now should always think that the great advantage of having
> this code and its users in the same repo tree is going away, i.e. we
> will not be able to improve the code by fixing mistakes that require
> changing its users.

Why? I mean, in the rasd case, changing function calling conventions as
part of updating the perf libraries is no act. I mean, we won't link
against a shared lib but build a static executable and thus the perf src
lib (let's call it that - a source library) we're using is a don't care.



Sent from a fat crate under my desk. Formatting is fine.
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