linux-kernel - Re: [GIT PULL] Performance Counters for Linux

lists.openwall.net		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 linux-cve-announce 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:	Thu, 11 Jun 2009 13:09:58 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	hch@...radead.org, a.p.zijlstra@...llo.nl,
	Al Viro <viro@...IV.linux.org.uk>, Ingo Molnar <mingo@...e.hu>,
	"David S. Miller" <davem@...emloft.net>, eranian@...glemail.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	paulus@...ba.org, tglx@...utronix.de
Subject: Re: [GIT PULL] Performance Counters for Linux

On Thu, 11 Jun 2009, Andrew Morton wrote:
> 
> It could be that shipping userspace code in the kernel bundle will
> improve that situation.  So let's give it a try.  If it turns out to be
> good, let's do it again.  If it turns out to be bad, let's move perf
> out of the kernel tree and not do it again.

Exactly. Right now, I use the oprofile experience as a reason for why we 
should try to do this. But hey, who knows, in one year, maybe people will 
use _this_ experience as a reason why we should never do it again.

We just don't know yet. But that's no reason not to try. Either way, we'll 
hopefully learn something.

Or to quote Edison:
 "I have not failed 700 times. I have not failed once. I have succeeded in 
  proving that those 700 ways will not work. When I have eliminated the 
  ways that will not work, I will find the way that will work."

			Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/