From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.com>, Petr Mladek <pmladek@suse.com>,
Tejun Heo <tj@kernel.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-kernel@vger.kernel.org,
Byungchul Park <byungchul.park@lge.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH v12 3/3] printk: make printk.synchronous param rw
Date: Sat, 23 Apr 2016 17:26:34 +0900 [thread overview]
Message-ID: <20160423082634.GA531@swordfish> (raw)
In-Reply-To: <20160423065633.GA6771@quack2.suse.cz>
Hello,
On (04/23/16 08:56), Jan Kara wrote:
> >
> > Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
>
> The patch looks good to me. One suggestion below:
>
> > @@ -1785,7 +1782,7 @@ asmlinkage int vprintk_emit(int facility, int level,
> > * operate in sync mode once panic() occurred.
> > */
> > if (console_loglevel != CONSOLE_LOGLEVEL_MOTORMOUTH &&
> > - printk_kthread) {
> > + !printk_sync && printk_kthread) {
> > /* Offload printing to a schedulable context. */
> > printk_kthread_need_flush_console = true;
> > wake_up_process(printk_kthread);
>
> It would seem more future-proof to hide '!printk_sync && printk_kthread'
> into a wrapper function as it is somewhat subtle detail that printk_kthread
> needn't exist while !printk_sync and I can imagine someone forgetting to
> check that in the future. Something like 'can_print_async()'? But I don't
> feel too strongly about that so feel free to add:
hm, yes. this is what I eventually do in "yet to be posted"
make-console_unlock()-async patch. I move printing kthread
wakeup-s and those async printing checks out of vprintk_emit()
and wake_up_klogd_work_func() to a special function:
static bool console_unlock_async_flush(void)
{
...
if (console_loglevel != CONSOLE_LOGLEVEL_MOTORMOUTH &&
!printk_sync && printk_kthread) {
/* Offload printing to a schedulable context. */
printk_kthread_need_flush_console = true;
console_locked = 0;
up_console_sem();
wake_up_process(printk_kthread);
return true;
}
return false;
}
so async_printk flags live in one place (which makes it easier
to maintain) and vprintk_emit()/wake_up_klogd_work_func() simply
do:
if (console_trylock())
console_unlock();
console_unlock() is the one who decides if it can do async
printk or a 'direct printing' via console_flush_and_unlock().
void console_unlock(void)
{
if (console_unlock_async_flush())
return;
console_flush_and_unlock();
}
console_flush_and_unlock() is what was previously known
as console_unlock() - emit the messages and call_console_drivers().
I guess I can send out an updated version of 0003 as a reply
to the initial patch and hide '!printk_sync && printk_kthread'.
> Reviewed-by: Jan Kara <jack@suse.cz>
>
> regardless whether you change this or not.
thanks.
-ss
next prev parent reply other threads:[~2016-04-23 8:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 13:52 [PATCH v12 0/3] printk: Make printk() completely async Sergey Senozhatsky
2016-04-22 13:52 ` [PATCH v12 1/3] " Sergey Senozhatsky
2016-04-26 14:13 ` Petr Mladek
2016-04-22 13:52 ` [PATCH v12 2/3] printk: Make wake_up_klogd_work_func() async Sergey Senozhatsky
2016-04-22 13:53 ` [PATCH v12 3/3] printk: make printk.synchronous param rw Sergey Senozhatsky
2016-04-23 6:56 ` Jan Kara
2016-04-23 8:26 ` Sergey Senozhatsky [this message]
2016-04-23 15:01 ` [PATCH] " Sergey Senozhatsky
2016-04-26 14:15 ` Petr Mladek
2016-04-27 1:09 ` Sergey Senozhatsky
-- strict thread matches above, loose matches on Subject: below --
2016-05-13 13:18 [PATCH v12 0/3] printk: Make printk() completely async Sergey Senozhatsky
2016-05-13 13:18 ` [PATCH v12 3/3] printk: make printk.synchronous param rw Sergey Senozhatsky
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=20160423082634.GA531@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=byungchul.park@lge.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tj@kernel.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 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.