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: [RFC][PATCH v8 1/2] printk: Make printk() completely async
Date: Fri, 1 Apr 2016 10:14:28 +0900 [thread overview]
Message-ID: <20160401011428.GB501@swordfish> (raw)
In-Reply-To: <20160329091439.GC12993@quack.suse.cz>
Hello Jan,
On (03/29/16 11:14), Jan Kara wrote:
> On Fri 25-03-16 00:43:22, Sergey Senozhatsky wrote:
> > @@ -1655,6 +1670,14 @@ asmlinkage int vprintk_emit(int facility, int level,
> > raw_spin_lock(&logbuf_lock);
> > logbuf_cpu = this_cpu;
> >
> > + /*
> > + * Set printing kthread sleep condition early, under the
> > + * logbuf_lock, so it (if RUNNING) will go to console_lock()
> > + * and spin on logbuf_lock.
> > + */
> > + if (!in_panic && printk_kthread && !need_flush_console)
> > + need_flush_console = true;
> > +
> > if (unlikely(recursion_bug)) {
> > static const char recursion_msg[] =
> > "BUG: recent printk recursion!";
>
> I like the cleaned up need_flush_console handling! Just a suggestion: It
> may be more logical to handle need_flush_console setting under logbuf_lock
> but after we actually store the message in the buffer, not before. Doesn't
> matter for correctness now but may be more future-proof.
I wanted to set it asap (when we know for sure that we will log_store()),
to have a bit more chances to avoid schedule() in printing thread. well,
that's just several log_store()-s, not a big deal, so I guess I can move
it to:
+ if (...)
+ need_flush_console = true;
logbuf_cpu = UINT_MAX;
raw_spin_unlock(&logbuf_lock);
lockdep_on();
local_irq_restore(flags);
-ss
next prev parent reply other threads:[~2016-04-01 1:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 15:43 [RFC][PATCH v8 0/2] printk: Make printk() completely async Sergey Senozhatsky
2016-03-24 15:43 ` [RFC][PATCH v8 1/2] " Sergey Senozhatsky
2016-03-29 9:14 ` Jan Kara
2016-04-01 1:14 ` Sergey Senozhatsky [this message]
2016-03-31 11:12 ` Petr Mladek
2016-03-31 11:52 ` Jan Kara
2016-04-04 9:41 ` Petr Mladek
2016-04-04 17:01 ` Sergey Senozhatsky
2016-04-01 1:08 ` Sergey Senozhatsky
2016-04-01 8:59 ` Petr Mladek
2016-04-01 9:36 ` Sergey Senozhatsky
2016-04-01 11:30 ` Petr Mladek
2016-03-24 15:43 ` [RFC][PATCH v8 2/2] printk: Make wake_up_klogd_work_func() async Sergey Senozhatsky
2016-03-31 11:14 ` Petr Mladek
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=20160401011428.GB501@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox