* Markus Metzger <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/