From: Andrew Morton <akpm@linux-foundation.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] printk: Support for full dynticks mode
Date: Mon, 4 Feb 2013 17:20:01 -0800 [thread overview]
Message-ID: <20130204172001.8bb358b0.akpm@linux-foundation.org> (raw)
In-Reply-To: <1360025478-32741-1-git-send-email-fweisbec@gmail.com>
On Tue, 5 Feb 2013 01:51:18 +0100
Frederic Weisbecker <fweisbec@gmail.com> wrote:
> printk: Wake up klogd using irq_work
That seems reasonable.
I'm wondering if we can now remove the printk_sched() special-case.
iirc, that was needed because wake_up(klogd) would deadlock when called
from sched internals. But now that wakeup is punted to the timer tick,
perhaps this is now unnecessary?
(Maybe there were other problems, but the 3ccf3e8306 is poor, and its
author is unavailable. There's a lesson there!)
next prev parent reply other threads:[~2013-02-05 1:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 0:51 [GIT PULL] printk: Support for full dynticks mode Frederic Weisbecker
2013-02-05 1:20 ` Andrew Morton [this message]
2013-02-05 1:22 ` Steven Rostedt
2013-02-05 1:37 ` Frederic Weisbecker
2013-02-05 2:09 ` Andrew Morton
2013-02-05 2:42 ` Steven Rostedt
2013-02-05 4:04 ` Andrew Morton
2013-02-05 12:05 ` Ingo Molnar
2013-02-05 3:14 ` Steven Rostedt
2013-02-05 3:19 ` Frederic Weisbecker
2013-02-05 3:24 ` Steven Rostedt
2013-02-05 3:29 ` Steven Rostedt
2013-02-05 12:13 ` Ingo Molnar
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=20130204172001.8bb358b0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox