linux-kernel - Re: [PATCH 6/6] x86: Allow disabling HW_BREAKPOINTS and 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:	Tue, 8 Oct 2013 12:24:51 -0400
From:	Dave Jones <davej@...hat.com>
To:	David Ahern <dsahern@...il.com>
Cc:	Ingo Molnar <mingo@...nel.org>, Andi Kleen <andi@...stfloor.org>,
	x86@...nel.org, linux-kernel@...r.kernel.org, peterz@...radead.org,
	Andi Kleen <ak@...ux.intel.com>, fweisbec@...il.com
Subject: Re: [PATCH 6/6] x86: Allow disabling HW_BREAKPOINTS and PERF_EVENTS

On Tue, Oct 08, 2013 at 10:22:23AM -0600, David Ahern wrote:
 > On 10/8/13 9:51 AM, Dave Jones wrote:
 > > On Tue, Oct 08, 2013 at 08:59:38AM +0200, Ingo Molnar wrote:
 > >
 > >   > You might want to concentrate your efforts from fighting perf
 > >   > functionality towards decreasing per tracepoint overhead instead,
 > >   > without hurting kernel functionality and maintainability.
 > >
 > > Making it easier to disable perf entirely would be desirable for one use case.
 > > I can't do a trinity run for more than a few hours for the last few months
 > > without hitting perf/ftrace bugs that no-one seems to be able to get their
 > > heads around.
 > 
 > Looks like trinity has an exclude syscall option. Seems like that option 
 > can be used to avoid perf_event_open (haven't tried though).

You'd think that, but for whatever reason, ftrace/perf oopses still happen.

	Dave

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