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]
Message-Id: <20090611125804.411095e8.akpm@linux-foundation.org>
Date:	Thu, 11 Jun 2009 12:58:04 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	hch@...radead.org, a.p.zijlstra@...llo.nl, viro@...IV.linux.org.uk,
	mingo@...e.hu, davem@...emloft.net, eranian@...glemail.com,
	linux-kernel@...r.kernel.org, paulus@...ba.org, tglx@...utronix.de
Subject: Re: [GIT PULL] Performance Counters for Linux

On Thu, 11 Jun 2009 10:06:55 -0700 (PDT)
Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> You haven't actually looked the real problem in the eye, and acknowledged 
> the disaster that is oprofile. Let's give a _new_ approach a chance, and 
> see if we can avoid the mistakes of yesteryear this time.

+1, metoo.

We've had numerous problems in the past where kernel developers have
shied away from altering or distributing userspace code.  One effect of
this which we see again and again is that people shove presentation and
parsing code into the kernel which should have been in userspace.

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.


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ