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:	Fri, 30 Nov 2007 11:34:03 +0100
From:	Andi Kleen <ak@...e.de>
To:	"Metzger, Markus T" <markus.t.metzger@...el.com>,
	tglx@...utronix.de
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, mingo@...e.hu, hpa@...or.com,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	"Michael Kerrisk" <mtk-manpages@....net>
Subject: Re: [patch 0/2] x86, ptrace:  support for branch trace store(BTS)

On Friday 30 November 2007 10:57:22 Metzger, Markus T wrote:
> 
> >Is there any userspace code avaialble which people can use to play with
> >this?
> 
> Not yet. We are talking to internal teams regarding gdb support.

But you already have reasonably realistic test code right?

We were burned a few times recently with new interfaces that turned
out to be not really usable from the user perspective.

Ideal situation to avoid that would be that at least one person other than 
the patch submitter has successfully written a program using it first.

e.g. I'm still feeling a bit uneasy about that global sysctl
embedded in the interface.

> 
> >How do you envisage it being used in the long term?  Do you 
> >expect any of
> >the standard performance tuning tools will be tweaked to 
> >understand this
> >feature and if so which ones?
> 
> I would expect debuggers to use it to show an execution trace of the 
> debuggee. The ptrace interface targets application debuggers;

application debuggers and possible performance tools. There are certainly
a lot of possibilities from this.


> If the feature turns out to be really useful, I would, of course, expect
> (or at least hope) that other CPU's would provide a similar feature.

I think some others do. But the details are always CPU specific. I doubt
much low level code will be possible to share. But it would be good
if the ptrace interface is generic enough for everybody (I think it was
though) 

 
> Most of the code is arch specific. If other CPU's share the general BTS
> layout,
> some of the ptrace_bts.c code could be shared.
> Since the implementation only supports x86, I think the code should go
> into
> arch/x86 - at least until other CPU's are supported.

Agreed.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ