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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <029E5BE7F699594398CA44E3DDF55444019B50A0@swsmsx413.ger.corp.intel.com>
Date:	Wed, 26 Mar 2008 09:39:46 -0000
From:	"Metzger, Markus T" <markus.t.metzger@...el.com>
To:	"Ingo Molnar" <mingo@...e.hu>, <roland@...hat.com>
Cc:	<ak@...e.de>, <hpa@...or.com>, <linux-kernel@...r.kernel.org>,
	<tglx@...utronix.de>, <markus.t.metzger@...il.com>,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	<akpm@...ux-foundation.org>, <mtk.manpages@...il.com>,
	<eranian@...glemail.com>,
	"Villacis, Juan" <juan.villacis@...el.com>
Subject: RE: [patch] x86, ptrace: support pebs in ds.c and disable ptraceand ds support

>-----Original Message-----
>From: Ingo Molnar [mailto:mingo@...e.hu] 
>Sent: Freitag, 21. März 2008 13:54


>> Ds.c is meant to be the resource allocator for per-thread and per-cpu
>> BTS and PEBS recording.
>> It is used by ptrace to provide execution tracing of debugged tasks.
>> It will be used by utrace for the same purpose.
>> It will be used by profilers (e.g. perfmon2).
>> It may be used by kernel debuggers to provide a kernel 
>execution trace.
>
>we could apply this if Roland Acks it - 

I moved Roland to the To: list. I hope we can resolve this in a technical discussion.


>but i guess a precondition for 
>that is to not include more ptrace extensions and to also 
>start working 
>on utrace support for it. Ptrace is something we want to reduce usage 
>of, not extend.

The patch is targeting application debuggers (in the first place). As far as I know, today's application debuggers are using ptrace. And I expect them to continue to use ptrace for some time.

I would not want to exclude existing debuggers from this feature; nor would I want to put a too big burden on debuggers if they wished to support execution tracing.

I will look into utrace as an additional interface.

Until utrace has been adopted by debuggers, I think ptrace (as its predecessor) is a good choice for an interim solution. 


regards,
markus.
---------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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