linux-kernel - Re: [patch 4/5] x86, ptrace: new ptrace BTS API

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] [day] [month] [year] [list]

Message-ID: <20071215072538.GA12110@elte.hu>
Date:	Sat, 15 Dec 2007 08:25:38 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Markus Metzger <markus.t.metzger@...el.com>
Cc:	ak@...e.de, hpa@...or.com, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, markus.t.metzger@...il.com,
	suresh.b.siddha@...el.com, roland@...hat.com,
	akpm@...ux-foundation.org, mtk.manpages@...il.com,
	Ulrich Drepper <drepper@...hat.com>
Subject: Re: [patch 4/5] x86, ptrace: new ptrace BTS API


* Markus Metzger <markus.t.metzger@...el.com> wrote:

> Here's the new ptrace BTS API that supports two different overflow 
> handling mechanisms (wrap-around and buffer-full-signal) to support 
> two different use cases (debugging and profiling).
> 
> It further combines buffer allocation and configuration.
> 
> Opens:
> - memory rlimit
> - overflow signal
> 
> What would be the right signal to use?

i think we tend to have such signal targets configurable (like in the 
POSIX timers APIs) - or we could use SIGIO. I've Cc:-ed Ulrich - maybe 
he has some specific ideas how to structure this.

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