linux-kernel - Re: [GIT PULL] perf fixes

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: <20130912211846.GA7890@gmail.com>
Date:	Thu, 12 Sep 2013 23:18:47 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	David Ahern <dsahern@...il.com>
Cc:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] perf fixes


* David Ahern <dsahern@...il.com> wrote:

> On 9/12/13 1:46 PM, Ingo Molnar wrote:
> >>>Mind outlining the approach you are thinking about?
> >>>
> >>>Firstly, please don't even think about autotools. (Just forget it exists.)
> >>
> >>hehe, no, that wasn't considered.
> >
> >/phew! :-)
> 
> kconf approach of course:
>   https://lkml.org/lkml/2013/4/1/600
> (minus the manual steps in that RFC).

I'm not sure what the end stage is where you'd like to arrive, but I don't 
think that forcing a separate configuration pass is an improvement :-/

By default a simple 'make' should build perf to the maximum extent 
possible, with no other input required from the user - with warnings 
displayed as package install suggestions.

This:

 Enable newt-based TUI (NEWT) [N/y] (NEW) y
 Enable GTK-based UI (GTK2) [N/y] (NEW) n
 Enable support for Bionic (e.g., Android platform) (BIONIC) [N/y] (NEW)
 Development support for libc is available - glibc or bionic (LIBC) [N/y] 
 (NEW) y
   Enable support for libelf (LIBELF) [N/y] (NEW) y
     Enable support for libunwind (LIBUNWIND) [N/y] (NEW) y
     Enable support for dwarf (DWARF) [N/y] (NEW) y
     Enable support for demangle (DEMANGLE) [N/y] (NEW) y
 Enable support for perl scripting engine (LIBPERL) [N/y] (NEW) y
 Enable support for python scripting engine (LIBPYTHON) [N/y] (NEW) y
 Enable support for libaudit (LIBAUDIT) [N/y/?] (NEW) y
 Enable support for libnuma (LIBNUMA) [N/y/?] (NEW) y
 Enable support for stack backtrace debugging (BACKTRACE) [N/y] (NEW) y

would be useful only as long as each listed option is actually 
_buildable_. I.e. it should not be possible for the user to configure perf 
in a way that makes the build fail.

I.e. this should go on top of a feature detection logic, allowing further 
customization, for features that the user might want to turn off.

Thanks,

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