From: lijiazi <jqqlijiazi@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
"Jiazi.Li" <jiazi.li@transsion.com>,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] ring-buffer: Add barrire in rb_move_tail
Date: Thu, 29 Sep 2022 17:12:01 +0800 [thread overview]
Message-ID: <20220929091201.GA21685@Jiazi.Li> (raw)
In-Reply-To: <20220928162908.07b12250@gandalf.local.home>
On Wed, Sep 28, 2022 at 04:29:08PM -0400, Steven Rostedt wrote:
> On Wed, 28 Sep 2022 10:59:35 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > > Will reply with an updated patch.
> >
> > Can you try this patch?
>
> Actually, that failed my testing (for other reasons), can you try this one?
>
Sure, thank you.
> -- Steve
>
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 3046deacf7b3..46b6f4107428 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -2648,6 +2648,9 @@ rb_reset_tail(struct ring_buffer_per_cpu *cpu_buffer,
> /* Mark the rest of the page with padding */
> rb_event_set_padding(event);
>
> + /* Make sure the padding is visible before the write update */
> + smp_wmb();
> +
> /* Set the write back to the previous setting */
> local_sub(length, &tail_page->write);
> return;
> @@ -2659,6 +2662,9 @@ rb_reset_tail(struct ring_buffer_per_cpu *cpu_buffer,
> /* time delta must be non zero */
> event->time_delta = 1;
>
> + /* Make sure the padding is visible before the tail_page->write update */
> + smp_wmb();
> +
> /* Set write to end of buffer */
> length = (tail + length) - BUF_PAGE_SIZE;
> local_sub(length, &tail_page->write);
> @@ -4627,6 +4633,29 @@ rb_get_reader_page(struct ring_buffer_per_cpu *cpu_buffer)
> arch_spin_unlock(&cpu_buffer->lock);
> local_irq_restore(flags);
>
> + /* The writer has preempt disable, wait for it. But not forever */
> + for (nr_loops = 0; nr_loops < 1000; nr_loops++) {
> + /* If the write is past the end of page, a writer is still updating it */
> + if (likely(!reader || rb_page_write(reader) <= BUF_PAGE_SIZE))
> + break;
> +
> + udelay(1);
> +
> + /* Get the latest version of the reader write value */
> + smp_rmb();
> + }
> +
> + /* The writer is not moving forward? Something is wrong */
> + if (RB_WARN_ON(cpu_buffer, nr_loops == 1000))
> + reader = NULL;
> +
> + /*
> + * Make sure we see any padding after the write update
> + * (see rb_reset_tail())
> + */
> + smp_rmb();
> +
> +
> return reader;
> }
>
next prev parent reply other threads:[~2022-09-29 9:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 12:08 [PATCH] ring-buffer: Add barrire in rb_move_tail Jiazi.Li
2022-09-01 15:13 ` Steven Rostedt
2022-09-02 3:47 ` lijiazi
2022-09-02 12:56 ` Steven Rostedt
2022-09-05 3:23 ` lijiazi
2022-09-06 16:25 ` Steven Rostedt
2022-09-07 3:03 ` lijiazi
2022-09-07 8:13 ` lijiazi
2022-09-15 8:25 ` lijiazi
2022-09-28 14:54 ` Steven Rostedt
2022-09-28 14:59 ` Steven Rostedt
2022-09-28 20:29 ` Steven Rostedt
2022-09-29 9:12 ` lijiazi [this message]
2022-09-30 21:49 ` Steven Rostedt
2022-10-08 1:21 ` lijiazi
2022-10-08 12:50 ` 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=20220929091201.GA21685@Jiazi.Li \
--to=jqqlijiazi@gmail.com \
--cc=jiazi.li@transsion.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/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).