linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: "Jiri Olsa" <jolsa@redhat.com>,
	"Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Toke Høiland-Jørgensen" <toke@redhat.com>,
	"Andrii Nakryiko" <andrii.nakryiko@gmail.com>,
	"Jiri Olsa" <jolsa@kernel.org>,
	"Arnaldo Carvalho de Melo" <acme@kernel.org>,
	Networking <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
	"Ingo Molnar" <mingo@kernel.org>,
	"Namhyung Kim" <namhyung@kernel.org>,
	"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
	"Jesper Dangaard Brouer" <brouer@redhat.com>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Martin KaFai Lau" <kafai@fb.com>,
	"Song Liu" <songliubraving@fb.com>, "Yonghong Song" <yhs@fb.com>,
	"Andrii Nakryiko" <andriin@fb.com>,
	"Quentin Monnet" <quentin.monnet@netronome.com>
Subject: [PATCH 0/3] tracing: perf: Rename ring_buffer to perf_buffer and trace_buffer
Date: Thu, 09 Jan 2020 21:03:08 -0500	[thread overview]
Message-ID: <20200110020308.977313200@goodmis.org> (raw)


As we discussed, to remove the generic structure "ring_buffer" from the kernel,
and switch it to "perf_buffer" and "trace_buffer", this patch series does
just that.

Anyone have any issues of me carrying this in my tree? I'll rebase it to
v5.5-rc6 when it comes out, as it depends on some commits in v5.5-rc5.

-- Steve

Steven Rostedt (VMware) (3):
      perf: Make struct ring_buffer less ambiguous
      tracing: Rename trace_buffer to array_buffer
      tracing: Make struct ring_buffer less ambiguous

----
 drivers/oprofile/cpu_buffer.c        |   2 +-
 include/linux/perf_event.h           |   6 +-
 include/linux/ring_buffer.h          | 110 ++++++-------
 include/linux/trace_events.h         |   8 +-
 include/trace/trace_events.h         |   2 +-
 kernel/events/core.c                 |  42 ++---
 kernel/events/internal.h             |  34 ++--
 kernel/events/ring_buffer.c          |  54 +++----
 kernel/trace/blktrace.c              |   8 +-
 kernel/trace/ftrace.c                |   8 +-
 kernel/trace/ring_buffer.c           | 124 +++++++--------
 kernel/trace/ring_buffer_benchmark.c |   2 +-
 kernel/trace/trace.c                 | 292 +++++++++++++++++------------------
 kernel/trace/trace.h                 |  38 ++---
 kernel/trace/trace_branch.c          |   6 +-
 kernel/trace/trace_events.c          |  20 +--
 kernel/trace/trace_events_hist.c     |   4 +-
 kernel/trace/trace_functions.c       |   8 +-
 kernel/trace/trace_functions_graph.c |  14 +-
 kernel/trace/trace_hwlat.c           |   2 +-
 kernel/trace/trace_irqsoff.c         |   8 +-
 kernel/trace/trace_kdb.c             |   8 +-
 kernel/trace/trace_kprobe.c          |   4 +-
 kernel/trace/trace_mmiotrace.c       |  12 +-
 kernel/trace/trace_output.c          |   2 +-
 kernel/trace/trace_sched_wakeup.c    |  20 +--
 kernel/trace/trace_selftest.c        |  26 ++--
 kernel/trace/trace_syscalls.c        |   8 +-
 kernel/trace/trace_uprobe.c          |   2 +-
 29 files changed, 437 insertions(+), 437 deletions(-)

             reply	other threads:[~2020-01-10  2:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10  2:03 Steven Rostedt [this message]
2020-01-10  2:03 ` [PATCH 1/3] perf: Make struct ring_buffer less ambiguous Steven Rostedt
2020-01-10  2:03 ` [PATCH 2/3] tracing: Rename trace_buffer to array_buffer Steven Rostedt
2020-01-10  2:03 ` [PATCH 3/3] tracing: Make struct ring_buffer less ambiguous Steven Rostedt
2020-01-10 14:49 ` [PATCH 0/3] tracing: perf: Rename ring_buffer to perf_buffer and trace_buffer Jiri Olsa

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=20200110020308.977313200@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=kafai@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=quentin.monnet@netronome.com \
    --cc=songliubraving@fb.com \
    --cc=toke@redhat.com \
    --cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).