mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bharath Ravi <rbharath@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Vaibhav Nagarnaik <vnagarnaik@google.com>,
	David Sharp <dhsharp@google.com>,
	Bharath Ravi <rbharath@google.com>,
	Laurent Chavey <chavey@google.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Allow instances to independently set trace options.
Date: Mon, 24 Mar 2014 11:13:43 -0700	[thread overview]
Message-ID: <1395684826-22931-1-git-send-email-rbharath@google.com> (raw)

Currently, the trace options are global, and shared among all
instances. This patchset allows instances to set certain trace options
independently, without affecting the global instance or other instances.
With this change, trace_overwrite will become an instance specific
option, while others remain global options.

This is achieved in three steps
1. Replace references to the global trace_flags mask with get/set
   accessors. This allows global trace_flags to be replaced by instance
   specific flags in step 2.
2. Replace the global trace_flags mask with instance specific
   trace_flags from the trace_array. Divide the set of trace options
   into global options, and instance options (that may be set independently
   by instances).
3. Make trace_overwrite an instance specific option.

Bharath Ravi (3):
  tracing: Replace usage of trace_flags with new accessors.
  tracing: Allow instances to have independent trace flags/trace
    options.
  tracing: Allow instances to independently set trace_overwrite.

 kernel/trace/blktrace.c              |   3 +-
 kernel/trace/ftrace.c                |   4 +-
 kernel/trace/trace.c                 | 127 +++++++++++++++++++++++++----------
 kernel/trace/trace.h                 |  48 ++++++-------
 kernel/trace/trace_events.c          |   2 +-
 kernel/trace/trace_functions_graph.c |  10 +--
 kernel/trace/trace_irqsoff.c         |   4 +-
 kernel/trace/trace_kdb.c             |   6 +-
 kernel/trace/trace_output.c          |   8 +--
 kernel/trace/trace_printk.c          |   8 +--
 kernel/trace/trace_sched_wakeup.c    |   3 +-
 kernel/trace/trace_syscalls.c        |   2 +-
 12 files changed, 143 insertions(+), 82 deletions(-)

-- 
1.9.1.423.g4596e3a


             reply	other threads:[~2014-03-24 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 18:13 Bharath Ravi [this message]
2014-03-24 18:13 ` [PATCH 1/3] tracing: Replace usage of trace_flags with new accessors Bharath Ravi
2014-04-25 18:46   ` Steven Rostedt
2014-03-24 18:13 ` [PATCH 2/3] tracing: Allow instances to have independent trace flags/trace options Bharath Ravi
2014-03-24 18:13 ` [PATCH 3/3] tracing: Allow instances to independently set trace_overwrite Bharath Ravi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1395684826-22931-1-git-send-email-rbharath@google.com \
    --to=rbharath@google.com \
    --cc=chavey@google.com \
    --cc=dhsharp@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=vnagarnaik@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®