All of lore.kernel.org
 help / color / mirror / Atom feed
From: Venkat Subbiah <vsubbiah@caviumnetworks.com>
To: "frank.rowand@am.sony.com" <frank.rowand@am.sony.com>
Cc: "Rowand, Frank" <Frank_Rowand@sonyusa.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH RT 2/2] fix printk flush of messages
Date: Mon, 21 May 2012 13:10:56 -0700	[thread overview]
Message-ID: <4FBAA150.6050308@caviumnetworks.com> (raw)
In-Reply-To: <4FB44FD0.4090800@am.sony.com>

On 05/16/2012 06:09 PM, Frank Rowand wrote:
> Updates console-make-rt-friendly.patch
>
> #ifdef CONFIG_PREEMPT_RT_FULL, printk() output is never flushed by
> printk() because:
So this is an issue for printk() itself and is not just for early_printk()?


    # some liberties taken in this pseudo-code to make it easier to follow
    printk()
       vprintk()
          raw_spin_lock(&logbuf_lock)
             # increment preempt_count():
             preempt_disable()
       result = console_trylock_for_printk()

As I read it console_trylock_for_printk() is called from printk() but in 
code it is called from vprintk()
>           retval = 0
>           # lock will always be false, because preempt_count() will be>= 1
>           lock = ...&&  !preempt_count()
>           if (lock)
>              retval = 1
>           return retval
>        # result will always be false since lock will always be false
>        if (result)
>           console_unlock()
>              # this is where the printk() output would be flushed
>
>
> On system boot some printk() output is flushed because register_console()
> and tty_open() call console_unlock().
>
>
> This change also fixes the problem that was previously fixed by
> preempt-rt-allow-immediate-magic-sysrq-output-for-preempt_rt_full.patch
>
> Signed-off-by: Frank Rowand<frank.rowand@am.sony.com>
>
> ---
>   kernel/printk.c |    2 	1 +	1 -	0 !
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: b/kernel/printk.c
> ===================================================================
> --- a/kernel/printk.c
> +++ b/kernel/printk.c
> @@ -847,7 +847,7 @@ static int console_trylock_for_printk(un
>   	int retval = 0, wake = 0;
>   #ifdef CONFIG_PREEMPT_RT_FULL
>   	int lock = !early_boot_irqs_disabled&&  !irqs_disabled_flags(flags)&&
> -		!preempt_count();
> +		(preempt_count()<= 1);
>   #else
>   	int lock = 1;
>   #endif
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  parent reply	other threads:[~2012-05-21 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  1:05 [PATCH RT 1/2] fix printk flush of messages Frank Rowand
2012-05-17  1:09 ` [PATCH RT 2/2] " Frank Rowand
2012-05-17  1:17   ` Frank Rowand
2012-05-21 20:10   ` Venkat Subbiah [this message]
2012-05-21 20:59     ` Frank Rowand
2012-08-21 14:30   ` Michael Thalmeier
2012-08-21 22:56     ` Frank Rowand

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=4FBAA150.6050308@caviumnetworks.com \
    --to=vsubbiah@caviumnetworks.com \
    --cc=Frank_Rowand@sonyusa.com \
    --cc=frank.rowand@am.sony.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.