linux-kernel - [patch 0/1] x86, ptrace: execution 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>] [day] [month] [year] [list]

Date:	Tue, 8 Apr 2008 10:59:06 +0200
From:	Markus Metzger <markus.t.metzger@...el.com>
To:	andi-suse@...stfloor.org, hpa@...or.com,
	linux-kernel@...r.kernel.org, mingo@...e.hu, tglx@...utronix.de
Cc:	markus.t.metzger@...el.com, markus.t.metzger@...il.com,
	suresh.b.siddha@...el.com, roland@...hat.com,
	akpm@...ux-foundation.org, mtk.manpages@...il.com,
	eranian@...glemail.com, juan.villacis@...el.com
Subject: [patch 0/1] x86, ptrace: execution trace support

Execution trace support for application debugging.

The following patch establishes the user interface and the low-level
hardware interface. What's missing is an intermediate layer based on
utrace.

The user interface uses ptrace to expose the feature to application
debuggers. From what I found on lwn.net, ptrace will remain as user
interface for utrace.

The low-level interface functions as resource allocator for the
hardware's IA32_DS_AREA MSR, which is used for PEBS performance
monitoring and for BTS execution tracing.

The low-level interface will be used by perfmon2 and is currently used
by this patch.

The patch currently implements execution trace support directly in
ptrace for the simple reason that utrace is not yet available.

>From the perspective of this patch, utrace is an intermediate layer
that will be introduced between ptrace and ds.c. As such, this layer
may be introduced at any time without affecting the other interfaces.

I fail to see a reason why we should not establish the two interfaces
that are meant to remain stable at this point in time.
- Intel is waiting for the user interface to support execution trace
  in their application debugger for MID.
- Perfmon2 is waiting for the low-level interface.
- Execution tracing is an extremely useful debugging feature that
  would greatly help application developers as well as kernel
  developers.

The patch does not depend on ptrace except for a small change to
ptrace_disable(); nor does it add dependencies to ptrace. It therefore
does not cause any additional effort in order to introduce the utrace
layer for the remainder of ptrace.

The two (three, if we consider perfmon2) projects would be able to
proceed independently and in parallel. Currently, we are preventing
progress on perfmon2 and on execution trace support for Moblin for no
apparent reason. 

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/