Bug 436862
Summary: | editorial comments on latency tracer comments | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Lana Brindley <lbrindle> |
Component: | Realtime_Tuning_Guide | Assignee: | Steven Rostedt <srostedt> |
Status: | CLOSED DUPLICATE | QA Contact: | Jeff Needle <jneedle> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | beta | CC: | mhideo |
Target Milestone: | --- | Keywords: | Documentation |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://rt.et.redhat.com/page/RHEL-RT_LatencyTracerHowto | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-22 00:52:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lana Brindley
2008-03-10 20:00:09 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 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 Steven, This is a friendly reminder :) LKB |