From: Sebastian Ott <sebott@linux.vnet.ibm.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: lockdep warning: console vs. mem hotplug
Date: Sat, 25 Mar 2017 11:59:07 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.20.1703251158060.2042@schleppi.fritz.box> (raw)
In-Reply-To: <20170325000442.GD6356@tigerII.localdomain>
On Sat, 25 Mar 2017, Sergey Senozhatsky wrote:
> On (03/21/17 13:44), Sergey Senozhatsky wrote:
> [..]
> > so we probably can
> >
> >
> > 1) move pr_info() out of zone->lock in __offline_isolated_pages().
> > meh...
> >
> >
> > 2) switch to printk_deferred() in __offline_isolated_pages().
> > meh.. there might a bunch of other printks done from under zone->lock.
> >
> >
> > 3) move add_timer() out of sclp_con_lock console in sclp_console_write().
> > well, there can be other consoles that do something similar.
> >
> >
> > 4) ... something smart.
>
>
> Sebastian, does this change make lockdep happy?
>
> it removes console drivers from the __offline_isolated_pages(). not the
> best solution I can think of, but the simplest one.
It does. No complaint from lockdep.
next prev parent reply other threads:[~2017-03-25 10:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 16:43 lockdep warning: console vs. mem hotplug Sebastian Ott
2017-03-21 4:44 ` Sergey Senozhatsky
2017-03-21 5:04 ` Sergey Senozhatsky
2017-03-25 0:04 ` Sergey Senozhatsky
2017-03-25 1:08 ` Steven Rostedt
2017-03-25 1:37 ` Sergey Senozhatsky
2017-03-25 10:59 ` Sebastian Ott [this message]
2017-03-28 14:22 ` Michal Hocko
2017-03-28 16:00 ` Petr Mladek
2017-03-29 7:31 ` Michal Hocko
2017-03-30 9:45 ` Petr Mladek
2017-03-30 3:59 ` Sergey Senozhatsky
2017-07-24 12:46 ` Sebastian Ott
2017-07-24 13:32 ` Sergey Senozhatsky
2017-03-24 16:39 ` Steven Rostedt
2017-03-24 16:57 ` Sebastian Ott
2017-03-25 0:00 ` Sergey Senozhatsky
2017-03-25 1:00 ` Steven Rostedt
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=alpine.LFD.2.20.1703251158060.2042@schleppi.fritz.box \
--to=sebott@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.ibm.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.