From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.linux-foundation.org, schwidefsky@de.ibm.com,
ubraun@linux.vnet.ibm.com, heiko.carstens@de.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] [RFC][PATCH] Add late pm notifiers for hibernate
Date: Tue, 14 Apr 2009 18:00:43 +0200 [thread overview]
Message-ID: <1239724843.4295.19.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0904091414340.2992-100000@iolanthe.rowland.org>
Hallo Alan,
Am Donnerstag, den 09.04.2009, 14:17 -0400 schrieb Alan Stern:
> On Wed, 8 Apr 2009, Michael Holzheu wrote:
>
> > From: Michael Holzheu <holzheu at linux.vnet.ibm.com>
> >
> > This patch is a suggestion to solve the issue reported by Ursula Braun:
> > https://lists.linux-foundation.org/pipermail/linux-pm/2009-March/020443.html
> >
> > On s390 we have device drivers that don't belong to a Linux bus. Therefore
> > we can't use the PM device callbacks (dev_pm_ops). The only way to get
> > informed that we hibernate or resume is the pm_notifier_call_chain.
>
> I'm curious to know what device drivers these are that don't have a
> bus. Could they use the platform bus? That's more or less what it's
> intended for -- devices that don't fit anywhere else.
Examples are:
* xpram: drivers/s390/block/xpram.c - Block device driver that exports
expanded ram as block devices.
* sclp: drivers/s390/char/sclp.c - Driver to talk to the s390
service element. E.g. used to control the console.
* and some others like DCSS driver etc ...
Your suggestion with the platform bus looks good. Probably we can use it
for those drivers. At least for xpram and sclp. For the other device
drivers we are still discussing.
> > Unfortunately some of our drivers need a frozen userspace to do their
> > hibernate actions and the current notifiers are called before userspace is
> > frozen. Another point is that we want our console driver to suspend as late
> > as possible so that we can see all the hibernate progress messages on the
> > console.
>
> It's possible to avoid suspending the console at all if you boot with
> "no_console_suspend" as a kernel parameter.
For s390 we have real console devices that do IO and get interrupts. We
have to suspend these devices. The problem is that when the console
device is suspended, we do not get any more messages - independent from
no_console_suspend.
In case of panic, we have implemented a hack, where we register a panic
notifier that enables the console again and writes out the last
messages. This ensures that when the kernel crashes during suspend or
resume we get at least the last messages. Not nice, but useful.
Michael
prev parent reply other threads:[~2009-04-14 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 15:37 Michael Holzheu
2009-04-09 18:17 ` [linux-pm] " Alan Stern
2009-04-14 16:00 ` Michael Holzheu [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=1239724843.4295.19.camel@localhost.localdomain \
--to=holzheu@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=schwidefsky@de.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=ubraun@linux.vnet.ibm.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
Powered by JetHome