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] [day] [month] [year] [list]
Date:	Sat, 22 Dec 2012 16:00:00 -0800
From:	Linus Torvalds <>
To:	David Ahern <>
Cc:	Ingo Molnar <>,
	Arnaldo Carvalho de Melo <>,
	Linux Kernel Mailing List <>,
	Peter Zijlstra <>,
	Thomas Gleixner <>,
	Andrew Morton <>
Subject: Re: [GIT PULL] perf changes for v3.8

Sure. I actually think both should be deprecated, and replaced with
explicit "trace guest" vs "trace host" flags, just to make it
consistent, but I don't care deeply.

The only thing I care about is that compatibility must never be broken
(which the current setup does), and that people who don't use
virtualization should never be asked to use flags that have anything
to do with virtualization (which the current work-around involves).


On Sat, Dec 22, 2012 at 11:22 AM, David Ahern <> wrote:
> any opinions on whether the approach is reasonable?
> On 12/16/12 9:43 PM, David Ahern wrote:
>> All that is needed is for the current exclude_guest flag to be
>> deprecated such that for older binaries on newer kernels it is ignored
>> (perhaps a warn on once), and then a new flag -- exclude_guest2 -- is
>> then used for the new logic.
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