linux-kernel - Re: [PATCH] tools: add x86_energy_perf_policy to program MSR_IA32_ENERGY_PERF

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:	Wed, 27 Oct 2010 09:43:11 -0200
From:	Arnaldo Carvalho de Melo <acme@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Len Brown <lenb@...nel.org>,
	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH] tools: add x86_energy_perf_policy to program
	MSR_IA32_ENERGY_PERF_BIAS

Em Wed, Oct 27, 2010 at 08:01:39AM +0200, Ingo Molnar escreveu:
> 
> * Andrew Morton <akpm@...ux-foundation.org> wrote:
> > On Sat, 23 Oct 2010 00:40:18 -0400 (EDT) Len Brown <lenb@...nel.org> wrote:
> > tools/power/x86, eh?  It seems a better place than under
> > Documentation/, where such things have thus far landed!

> > I looked briefly, wondering about the kbuild situation.  It doesn't
> > appear to be wired up, so one has to manually enter that directory
> > and type `make'?

> > I guess that's OK as an interim thing but longer-term I suppose we
> > should have some more complete build and deployment system.  So
> > (thinking out loud) a `make' would invoke a `make tools', and that
> > `make tools' would build the tools which are specific to the target
> > arch[*], and any generic ones.  And a `make tools_install' would
> > install those tools in, I guess, /lib/modules/$(uname -r)/bin.
 
> In terms of build and documentation environment, tools/perf/ has one
> cloned/inherited from Git, which is rather good and functional.
 
> Sharing it with the kernel's build system depends on the kbuild
> developers being interested in it.

Yes, that is how it is today, I glued it to the main makefile in at
least one case:

[acme@...pio linux]$ make help | grep perf
  perf-tar-src-pkg    - Build perf-2.6.36-rc7.tar source tarball
  perf-targz-src-pkg  - Build perf-2.6.36-rc7.tar.gz source tarball
  perf-tarbz2-src-pkg - Build perf-2.6.36-rc7.tar.bz2 source tarball
[acme@...pio linux]$

I'd love to glue it some more, even using Kconfig and 'make toolsconfig'
for configuring the tools:

	. Want the TUI?
        . Want to link with DWARF? Needed for features x, y and z

Getting it done this way will provide examples that hopefully would lead
to more kernel coding practices and infrastructure being adopted by
(hell is freezing) userland programmers.

This is specially important now that there are more kernel programmers
writing userland code, lets hope that at least them continue to use
those practices and infrastructures ;-)

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