Date: Sat, 15 Dec 2007 08:25:38 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: ak@suse.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
       tglx@linutronix.de, markus.t.metzger@gmail.com,
       suresh.b.siddha@intel.com, roland@redhat.com, akpm@linux-foundation.org,
       mtk.manpages@gmail.com, Ulrich Drepper <drepper@redhat.com>
Subject: Re: [patch 4/5] x86, ptrace: new ptrace BTS API
Message-ID: <20071215072538.GA12110@elte.hu>
References: <20071214180531.A20647@sedona.ch.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20071214180531.A20647@sedona.ch.intel.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 851
Lines: 25


* Markus Metzger <markus.t.metzger@intel.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/