From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Petr Mladek <pmladek@suse.com>,
Chengming Zhou <zhouchengming@bytedance.com>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@linux.ie, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
sergey.senozhatsky@gmail.com, rostedt@goodmis.org,
mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
bsegall@google.com, mgorman@suse.de, songmuchun@bytedance.com,
john.ogness@linutronix.de
Subject: Re: [External] Re: [PATCH 2/2] sched: mark PRINTK_DEFERRED_CONTEXT_MASK in __schedule()
Date: Wed, 30 Sep 2020 09:48:52 +0900 [thread overview]
Message-ID: <20200930004852.GA987@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20200929150933.GR2628@hirez.programming.kicks-ass.net>
On (20/09/29 17:09), Peter Zijlstra wrote:
> > 2. The registration and unregistration of consoles should not longer
> > be handled by console_lock (semaphore). It should be possible to
> > call most consoles without a sleeping lock. It should remove all
> > these deadlocks between printk() and scheduler().
>
> I'm confused, who cares about registation? That only happens once at
> boot, right?
You can modprobe or rmmod (register/unregister) netconsole anytime,
for example.
-ss
prev parent reply other threads:[~2020-09-30 0:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 16:11 [PATCH 1/2] printk: Add printk_deferred_{enter, exit} Chengming Zhou
2020-09-27 16:11 ` [PATCH 2/2] sched: mark PRINTK_DEFERRED_CONTEXT_MASK in __schedule() Chengming Zhou
2020-09-28 7:32 ` Peter Zijlstra
2020-09-28 7:52 ` Joe Perches
2020-09-28 8:00 ` Peter Zijlstra
2020-09-28 8:06 ` Peter Zijlstra
2020-09-28 8:54 ` [External] " Chengming Zhou
2020-09-28 9:01 ` Peter Zijlstra
2020-09-28 10:04 ` Chengming Zhou
2020-09-28 10:25 ` Peter Zijlstra
2020-09-28 23:50 ` Sergey Senozhatsky
2020-09-29 14:27 ` Petr Mladek
2020-09-29 15:09 ` Peter Zijlstra
2020-09-30 0:48 ` Sergey Senozhatsky [this message]
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=20200930004852.GA987@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=airlied@linux.ie \
--cc=bsegall@google.com \
--cc=daniel@ffwll.ch \
--cc=dietmar.eggemann@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=john.ogness@linutronix.de \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mripard@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=songmuchun@bytedance.com \
--cc=tzimmermann@suse.de \
--cc=vincent.guittot@linaro.org \
--cc=zhouchengming@bytedance.com \
/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;
as well as URLs for NNTP newsgroup(s).