mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Song Chen <chensong_2000@189.cn>
Cc: mingo@redhat.com, mhiramat@kernel.org,
	linux-kernel@vger.kernel.org, xiehuan09@gmail.com
Subject: Re: [PATCH] trace/ring_buffer: remove unused arguments
Date: Thu, 20 Oct 2022 10:15:49 -0400	[thread overview]
Message-ID: <20221020101549.06e3fa5b@gandalf.local.home> (raw)
In-Reply-To: <1666274811-24138-1-git-send-email-chensong_2000@189.cn>

On Thu, 20 Oct 2022 22:06:51 +0800
Song Chen <chensong_2000@189.cn> wrote:

> As a argument, event has nothing to do with either
> ring_buffer_unlock_commit or rb_commit and cleaning
> it up has no side effect.

OK, so this is because of a389d86f7fd0 ("ring-buffer: Have nested events
still record running time stamp") which removed the usage of event in rb_commit():

 static void rb_commit(struct ring_buffer_per_cpu *cpu_buffer,
                      struct ring_buffer_event *event)
 {
        local_inc(&cpu_buffer->entries);
-       rb_update_write_stamp(cpu_buffer, event);
        rb_end_commit(cpu_buffer);
 }


I guess this doesn't hurt.

-- Steve

> 
> Signed-off-by: Song Chen <chensong_2000@189.cn>
> ---
>  include/linux/ring_buffer.h          |  3 +--
>  kernel/trace/ring_buffer.c           | 12 +++++-------
>  kernel/trace/ring_buffer_benchmark.c |  2 +-
>  kernel/trace/trace.c                 |  2 +-
>  4 files changed, 8 insertions(+), 11 deletions(-)

  reply	other threads:[~2022-10-20 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 14:06 Song Chen
2022-10-20 14:15 ` Steven Rostedt [this message]
2022-10-20 15:25   ` chensong
2022-10-20 15:43     ` Steven Rostedt

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=20221020101549.06e3fa5b@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=chensong_2000@189.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=xiehuan09@gmail.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®