All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <cminyard@mvista.com>
To: minyard@acm.org, rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
	tglx@linutronix.d, C.Emde@osadl.org, bigeasy@linutronix.de,
	jkacur@redhat.com, paul.gortmaker@windriver.com
Subject: Re: [PATCH] tracing: Always run per-cpu ring buffer resize with schedule_work_on()
Date: Mon, 28 Jul 2014 16:52:01 -0500	[thread overview]
Message-ID: <53D6C601.7090803@mvista.com> (raw)
In-Reply-To: <1405537633-31518-1-git-send-email-cminyard@mvista.com>

Ping, I haven't heard anything on this.

-corey

On 07/16/2014 02:07 PM, minyard@acm.org wrote:
> From: Corey Minyard <cminyard@mvista.com>
>
> The code for resizing the trace ring buffers has to run the per-cpu
> resize on the CPU itself.  The code was using preempt_off() and
> running the code for the current CPU directly, otherwise calling
> schedule_work_on().
>
> At least on RT this could result in the following:
>
> |BUG: sleeping function called from invalid context at kernel/rtmutex.c:673
> |in_atomic(): 1, irqs_disabled(): 0, pid: 607, name: bash
> |3 locks held by bash/607:
> |CPU: 0 PID: 607 Comm: bash Not tainted 3.12.15-rt25+ #124
> |(rt_spin_lock+0x28/0x68)
> |(free_hot_cold_page+0x84/0x3b8)
> |(free_buffer_page+0x14/0x20)
> |(rb_update_pages+0x280/0x338)
> |(ring_buffer_resize+0x32c/0x3dc)
> |(free_snapshot+0x18/0x38)
> |(tracing_set_tracer+0x27c/0x2ac)
>
> probably via
> |cd /sys/kernel/debug/tracing/
> |echo 1 > events/enable ; sleep 2
> |echo 1024 > buffer_size_kb
>
> If we just always use schedule_work_on(), there's no need for the
> preempt_off().  So do that.
>
> Reported-by: Stanislav Meduna <stano@meduna.org>
> Signed-off-by: Corey Minyard <cminyard@mvista.com>
> ---
>  kernel/trace/ring_buffer.c | 24 ++++--------------------
>  1 file changed, 4 insertions(+), 20 deletions(-)
>
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 7c56c3d..35825a8 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -1693,22 +1693,14 @@ int ring_buffer_resize(struct ring_buffer *buffer, unsigned long size,
>  			if (!cpu_buffer->nr_pages_to_update)
>  				continue;
>  
> -			/* The update must run on the CPU that is being updated. */
> -			preempt_disable();
> -			if (cpu == smp_processor_id() || !cpu_online(cpu)) {
> +			/* Can't run something on an offline CPU. */
> +			if (!cpu_online(cpu)) {
>  				rb_update_pages(cpu_buffer);
>  				cpu_buffer->nr_pages_to_update = 0;
>  			} else {
> -				/*
> -				 * Can not disable preemption for schedule_work_on()
> -				 * on PREEMPT_RT.
> -				 */
> -				preempt_enable();
>  				schedule_work_on(cpu,
>  						&cpu_buffer->update_pages_work);
> -				preempt_disable();
>  			}
> -			preempt_enable();
>  		}
>  
>  		/* wait for all the updates to complete */
> @@ -1746,22 +1738,14 @@ int ring_buffer_resize(struct ring_buffer *buffer, unsigned long size,
>  
>  		get_online_cpus();
>  
> -		preempt_disable();
> -		/* The update must run on the CPU that is being updated. */
> -		if (cpu_id == smp_processor_id() || !cpu_online(cpu_id))
> +		/* Can't run something on an offline CPU. */
> +		if (!cpu_online(cpu_id))
>  			rb_update_pages(cpu_buffer);
>  		else {
> -			/*
> -			 * Can not disable preemption for schedule_work_on()
> -			 * on PREEMPT_RT.
> -			 */
> -			preempt_enable();
>  			schedule_work_on(cpu_id,
>  					 &cpu_buffer->update_pages_work);
>  			wait_for_completion(&cpu_buffer->update_done);
> -			preempt_disable();
>  		}
> -		preempt_enable();
>  
>  		cpu_buffer->nr_pages_to_update = 0;
>  		put_online_cpus();

  reply	other threads:[~2014-07-28 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 19:07 [PATCH] tracing: Always run per-cpu ring buffer resize with schedule_work_on() minyard
2014-07-28 21:52 ` Corey Minyard [this message]
2014-07-29  8:59   ` Sebastian Andrzej Siewior
  -- strict thread matches above, loose matches on Subject: below --
2014-07-28 21:32 minyard

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=53D6C601.7090803@mvista.com \
    --to=cminyard@mvista.com \
    --cc=C.Emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=minyard@acm.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.d \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.