Dear Roland and dear utrace developers,
please help me. Either I have not understood the meaning of UTRACE_STOP
or it is completely useless due to a race condition.
There are always two entities in a utrace interaction: the traced
process and the tracing module.
When a traced event occurs in the
Renzo Davoli writes:
> [...]
> If the report function returns UTRACE_STOP the traced process stays in a
> quiescent state and the module wakes it up by a
> utrace_control(...,UTRACE_RESUME) call *later*.
> [...]
> If the module wakes the traced process too quickly, utrace has not yet put
> it in
On Wed, Feb 11, 2009 at 09:45:15AM -0500, Frank Ch. Eigler wrote:
> This may not answer your question, but I believe it is not proper to
> to make this call at any time t>1, only once you receive the quiesce
> callback.
Maybe I am wrong but the quiesce callback gets called *before* the other
repor
Dear Roland, dear utrace developers,
I have now a complete patch that seems to be quite stable.
At least Kmview have passed through the tests without getting stuck randomly
for the race condition.
All the other comments about utrace&virtualization (see my message of Feb 04)
are already pending
Thanks very much for the feedback, Renzo. You seem to be about the only
person to thoroughly exercise this part of the API so far. I'm sure it can
use some refinement.
> please help me. Either I have not understood the meaning of UTRACE_STOP
> or it is completely useless due to a race condition.
Dear Roland, dear utrace developers,
I have updated my patch #1 (it solves the race condition on utrace_stop but
not the nesting issue) for the latest version of utrace.
renzo
On Fri, Feb 13, 2009 at 09:29:25PM +0100, Renzo Davoli wrote:
> I have now a complete patch that seems to be quite stab
Dear Roland, dear utrace developers,
This is an updated patch. It solves the race condition + it gives a quick (a
bit dirty)
solution to issues 3&4.
3- Nesting, is it really useful to run all the reports in a row and
(eventually) stop and the end waiting for all the engines?
The
Dear Roland, dear utrace developers,
I have update also the second patch (which includes the first).
This patch fixes the utrace_stop race condition and
implements a consistent model of tracing engine nesting.
renzo
On Sat, Feb 14, 2009 at 10:11:55AM +0100, Renzo Davoli wrote:
>
> This
Dear Roland, dear utrace developers,
I have updated my patch #1 (it solves the race condition on utrace_stop but
not the nesting issue) for the latest version of utrace.
I am trying to get the patches updated downloading, compiling and testing
the fixes every week or so...
Things would be easier
Hi Renzo,
This patch needs Roland's review, but I'd like to participate...
On 03/12, Renzo Davoli wrote:
>
> I have updated my patch #1 (it solves the race condition on utrace_stop but
> not the nesting issue) for the latest version of utrace.
>
> I am trying to get the patches updated downloadin
10 matches
Mail list logo
