[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <y0mbq8s0x8e.fsf@ton.toronto.redhat.com>
Date: Sat, 15 Dec 2007 10:54:41 -0500
From: fche@...hat.com (Frank Ch. Eigler)
To: eranian@....hp.com
Cc: linux-kernel@...r.kernel.org, davem@...emloft.net,
paulus@...ba.org, akpm@...ux-foundation.org, gregkh@...e.de,
mucci@...utk.edu, wcohen@...hat.com, robert.richter@....com,
andi@...stfloor.org, eranian@...il.com, roland@...hat.com
Subject: Re: [perfmon2] perfmon2 merge news
Stephane Eranian <eranian@....hp.com> writes:
> [...]
>> > [...] AFAIK, there is no single call to stop T1 and wait until it
>> > is completely off the CPU, unless we go through the (internal)
>> > ptrace interface.
>>
>> The utrace code supports this style of thread manipulation better
>> than ptrace.
>
> Afre you saying that utrace provides a utrace_thread_stop(tid) call
> that returns only when the thread tid is off the CPU. And then there
> is a utrace_thread_resume(tid) call. If that's the case then that is
> what I need.
While I see no single call, it can be synthesized from a sequence of
them: utrace_attach, utrace_set_flags (... UTRACE_ACTION_QUESCE ...),
then waiting for a callback. Roland, is there a more compact way?
> How are we with regards to utrace integration?
Roland McGrath is working on breaking the patches down.
- FChE
--
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