From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-pm <linux-pm@lists.osdl.org>
Subject: Re: [PATCH] s2ram: add arch irq disable/enable hooks
Date: Fri, 20 Apr 2007 23:08:51 +0200 [thread overview]
Message-ID: <200704202308.52534.rjw@sisk.pl> (raw)
In-Reply-To: <1177102268.5902.36.camel@johannes.berg>
On Friday, 20 April 2007 22:51, Johannes Berg wrote:
> On Fri, 2007-04-20 at 22:36 +0200, Rafael J. Wysocki wrote:
>
> > Well, I can't say why exactly suspend_enter() usues irq_save/restore, but it
> > looks like that's not needed.
>
> powerpc works fine just with local_irq_disable/enable, never did
> anything else and my new patches just ignore the *flags argument.
>
> > For the suspend to disk we call
> > local_irq_disable/enable() in the corresponding places and, for example,
> > acpi_pm_enter apparently uses irq_save/restore() itself too.
>
> Why would acpi_pm_enter do that? It can always assume irqs are disabled.
> Or does it need to enable them for something (hey, that would mean Ben
> is right in that it probably wants to use these new hooks...)
>
> > > The only users of this function are in the power management core code (main.c
> > > and user.c) and they certainly always call it with interrupts enabled, the
> > > entry point for other users is pm_suspend() and that surely cannot be called
> > > with interrupts disabled. Rafael?
> >
> > That's correct, plus pm_suspend() also uses enter_state().
>
> Sure, but it can't be called with interrupts disabled.
>
> > In fact suspend_enter() has been made extern so that we can call it from
> > kernel/power/user.c and no one else is supposed to use it.
>
> Right.
>
> So, any argument against re-spinning this patch, removing the unsigned
> long *flags stuff and using local_irq_disable/enable?
Not from me.
Rafael
next prev parent reply other threads:[~2007-04-20 21:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 11:00 [PATCH] s2ram: add arch irq disable/enable hooks Johannes Berg
2007-04-19 21:55 ` Andrew Morton
2007-04-20 15:34 ` Johannes Berg
2007-04-20 6:57 ` Greg KH
2007-04-20 15:31 ` Johannes Berg
2007-04-20 17:39 ` Greg KH
2007-04-20 19:37 ` Johannes Berg
2007-04-20 19:44 ` Andrew Morton
2007-04-20 19:51 ` Johannes Berg
2007-04-20 20:36 ` Rafael J. Wysocki
2007-04-20 20:51 ` Johannes Berg
2007-04-20 21:08 ` Rafael J. Wysocki [this message]
2007-04-21 13:57 ` Johannes Berg
2007-04-21 14:07 ` Pavel Machek
2007-04-21 15:41 ` David Brownell
2007-04-21 16:16 ` Johannes Berg
2007-04-21 16:55 ` David Brownell
2007-04-21 17:01 ` Johannes Berg
2007-04-21 17:06 ` David Brownell
2007-04-21 17:49 ` Johannes Berg
2007-04-21 21:47 ` Pavel Machek
2007-04-21 22:04 ` Johannes Berg
2007-04-21 21:45 ` Pavel Machek
2007-04-22 3:10 ` David Brownell
2007-04-22 13:09 ` Pavel Machek
2007-04-26 11:02 ` David Woodhouse
2007-04-21 21:44 ` Pavel Machek
2007-04-22 3:05 ` David Brownell
2007-04-22 13:13 ` Pavel Machek
2007-04-24 13:51 ` Johannes Berg
2007-04-24 18:16 ` Pavel Machek
2007-04-25 3:45 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 21:54 [PATCH] pm_ops: add irq enable/disable hooks Johannes Berg
2007-04-17 17:18 ` [PATCH] s2ram: add arch irq disable/enable hooks Johannes Berg
2007-04-18 11:27 ` Pavel Machek
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=200704202308.52534.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=johannes@sipsolutions.net \
--cc=linux-pm@lists.osdl.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