linux-kernel - RE: [tip:tracing/core] x86, bts: reenable ptrace branch trace support

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: <1244640558.13761.11833.camel@twins>
Date:	Wed, 10 Jun 2009 15:29:18 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	"Metzger, Markus T" <markus.t.metzger@...el.com>
Cc:	Ingo Molnar <mingo@...e.hu>, "mingo@...hat.com" <mingo@...hat.com>,
	"hpa@...or.com" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"oleg@...hat.com" <oleg@...hat.com>,
	"linux-tip-commits@...r.kernel.org" 
	<linux-tip-commits@...r.kernel.org>
Subject: RE: [tip:tracing/core] x86, bts: reenable ptrace branch trace
 support

On Wed, 2009-06-10 at 14:22 +0100, Metzger, Markus T wrote:
> 
> The Debug Store interface is completely in-kernel. It does not expose
> anything to the outside world.
> 
> What we expose is a ptrace interface for branch tracing.
> That this is built on top of Debug Store is completely hidden.
> The Debug Store interface may be changed without impacting the
> user-visible part at any time.
> 
> I do think that a ptrace interface makes sense since debuggers are the
> targeted users for branch tracing.
> 
> I don't see why we should not merge the fixes now and then rework the
> in-kernel parts as needed for supporting PEBS.

Ok, so what is all that account_locked_memory() for?
--
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/