linux-kernel - Re: [PATCH 3/6] x86: Allow the user not to build hw

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, 14 Jul 2011 23:51:37 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Jason Wessel <jason.wessel@...driver.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 3/6] x86: Allow the user not to build hw_breakpoints

On Thu, Jul 14, 2011 at 02:26:11PM -0700, H. Peter Anvin wrote:
> On 07/14/2011 08:03 AM, Frederic Weisbecker wrote:
> > So that hw_breakpoints and perf can be not built on
> > specific embedded systems.
> 
> I want to emphasize I am very, very unhappy about this.  It should be
> possible to not build perf while still have breakpoints available...
> breakpoints are way more important than perf.

I know and that's a long term goal. I believe Will Deacon is currently working
on breakpoints to avoid archs to translate ptrace user arch input into perf generic
information (which afterward is eventually translated back to arch information).
This is a necessary first step to have a ptrace breakpoint implementation independant of
perf. Once we'll have that and all archs are converted to that new mode, we can work
toward having breakpoints not requiring perf to work.

Until we reach that point, it's still nice to have optable breakpoints. I think
it is a desired feature given the feedbacks I get from Prasad for example.
If that makes it possible to try a kernel without perf in x86, good too.

But this is not intended to be a solution of the breakpoint - perf dependency. That
dependency was a design mistake that needs more to be fixed.
We want to be able to have breakpoints without perf in the end. This just requires
deeper and longer term work that is currently in progress.
--
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/