Bug 436862 - editorial comments on latency tracer comments
Summary: editorial comments on latency tracer comments
Status: CLOSED DUPLICATE of bug 442990
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Realtime_Tuning_Guide
Version: beta
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Steven Rostedt
QA Contact: Jeff Needle
URL: http://rt.et.redhat.com/page/RHEL-RT_...
Whiteboard:
Keywords: Documentation
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-10 20:00 UTC by Lana Brindley
Modified: 2013-10-23 23:06 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2008-04-22 00:52:23 UTC


Attachments (Terms of Use)

Description Lana Brindley 2008-03-10 20:00:09 UTC
Description of problem:

There are a number of "editorial ocmments" on the latency tracer howto. Can I
please have someone respond to the issues raised in order to finish this chapter.

Assigned to Clark for distribution :)

LKB

Comment 1 Clark Williams 2008-03-11 18:29:22 UTC
Lana,

the Latency Tracer functionality is being rewritten by Steven Rostedt. I can
think of no one better equipped to provide content.

Reassigning to srostedt.

Clark


Comment 2 Lana Brindley 2008-03-11 20:48:37 UTC
Thanks Clark.

Steven, in your re-write, can you please explain the statement below for me too?

"Another way of using the tracing infrastructure is by enabling
/proc/sys/kernel/trace_user_triggered. That will trace only processes that
explicitly used the prctl(0, 1) syscall just before the critical session where
tracing is desired and prctl(0, 0) after it."

I don't really understand what effect the prctl() calls have on both the process
and the tracer.

Thanks,
Lana

Comment 3 Lana Brindley 2008-03-27 03:06:11 UTC
Steven, This is a friendly reminder :) LKB

Comment 4 Lana Brindley 2008-04-22 00:52:23 UTC

*** This bug has been marked as a duplicate of 442990 ***


Note You need to log in before you can comment on or make changes to this bug.