From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: Alexey Starikovskiy <aystarik@gmail.com>,
Damien Wyart <damien.wyart@free.fr>,
Torsten Kaiser <just.for.lkml@googlemail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>, Frans Pop <elendil@planet.nl>,
linux-acpi@vger.kernel.org
Subject: Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7)
Date: Tue, 25 Sep 2007 16:52:04 +0200 [thread overview]
Message-ID: <200709251652.05589.rjw@sisk.pl> (raw)
In-Reply-To: <46F918F8.1080808@suse.de>
On Tuesday, 25 September 2007 16:19, Alexey Starikovskiy wrote:
> Rafael J. Wysocki wrote:
> > On Tuesday, 25 September 2007 15:15, Alexey Starikovskiy wrote:
> >> Rafael J. Wysocki wrote:
> >>> On Tuesday, 25 September 2007 14:53, Alexey Starikovskiy wrote:
> >>>> Rafael J. Wysocki wrote:
> >>>>> On Tuesday, 25 September 2007 14:05, Alexey Starikovskiy wrote:
> >>>>>> Rafael J. Wysocki wrote:
> >>>>>>> On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote:
> >>>>>>>> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote:
> >>>>>>>>>>> No, I do not have CONFIG_ACPI_SLEEP set,
> >>>>>>>>>>> because I do not have CONFIG_PM_SLEEP set,
> >>>>>>>>>>> because I do not want SUSPEND and/or HIBERNATION.
> >>>>>>>>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same
> >>>>>>>>>> reason (and this worked fine without them in rc7). I do not think
> >>>>>>>>>> these settings should have changed between rc7 and rc8.
> >>>>>>>> Well, we haven't changed much.
> >>>>>>>>
> >>>>>>>>> Also, another test I just did: on another computer, rc8 is fine
> >>>>>>>>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can
> >>>>>>>>> provide config if needed.
> >>>>>>>> On the box that fails to power off, can you please test -rc8 with these two
> >>>>>>>> commits reverted:
> >>>>>>>>
> >>>>>>>> commit 5a50fe709d527f31169263e36601dd83446d5744
> >>>>>>>> ACPI: suspend: consolidate handling of Sx states addendum
> >>>>>>>>
> >>>>>>>> commit f216cc3748a3a22c2b99390fddcdafa0583791a2
> >>>>>>>> ACPI: suspend: consolidate handling of Sx states.
> >>>>>>>>
> >>>>>>>> and see if it works?
> >>>>>>> If it does, please test the patch from this message
> >>>>>>>
> >>>>>>> http://marc.info/?l=linux-kernel&m=119052978117735&w=4
> >>>>>>>
> >>>>>>> on top of vanilla 2.6.23-rc8.
> >>>>>> You will need one more patch on top of just mentioned one.
> >>>>> Hm, why did you put acpi_target_sleep_state under CONFIG_SUSPEND?
> >>>>>
> >>>>> CONFIG_HIBERNATION needs acpi_target_sleep_state too.
> >>>> Agree, attaching updated patch.
> >>> Well, please use "ifdef CONFIG_PM_SLEEP" instead of
> >>> "if defined(CONFIG_SUSPEND)||defined(CONFIG_HIBERNATION)",
> >>> as you did with the second block.
> >> I was thinking about that, but it seem to be less clear...
> >> We need this variable only for suspend or hibernation, nothing else.
> >> with pm_sleep it is not visible at all.
> >>
> >> Thoughts?
> >
> > Well, PM_SLEEP is defined as (SUSPEND || HIBERNATION), please have a look
> > at kernel/power/Kconfig, and it was introduced exactly for the conditions like
> > this.
> I've seen this then I wrote the patch :) See my point, it is not clear,
> that PM_SLEEP is equivalent to SUSPEND || HIBERNATION, one needs to
> grep Kconfig files to find that -- it means that code becomes less readable,
> and I would like to avoid that.
I see your point. Still, you are using PM_SLEEP in the same file, so someone
reading the code for the first time will have to find out what it is anyway.
OTOH, the only function of PM_SLEEP is to be a replacement for
(SUSPEND || HIBERNATION). It has no other meaning whatsoever.
[Well, sorry, I couldn't invent a better name.]
> > IOW, if we want something to be used for anything else than suspend or
> > hibernation, it shouldn't be defined under PM_SLEEP.
> Agree, but we should distinguish there it is better to use PM_SLEEP,
> and there it is better to use (SUSPEND || HIBERNATION) just to be more expressive...
Well, since PM_SLEEP is used as (SUSPEND || HIBERNATION) everywhere else,
I think that it would actually be confusing not to use it here. :-)
Greetings,
Rafael
next prev parent reply other threads:[~2007-09-25 14:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 6:51 ACPI power off regression in 2.6.23-rc8 (NOT in rc7) Damien Wyart
2007-09-25 7:33 ` Andrew Morton
2007-09-25 8:36 ` Alexey Starikovskiy
2007-09-25 9:08 ` Torsten Kaiser
2007-09-25 9:27 ` Damien Wyart
2007-09-25 9:58 ` Damien Wyart
2007-09-25 11:45 ` Rafael J. Wysocki
2007-09-25 12:02 ` Damien Wyart
2007-09-25 15:05 ` Damien Wyart
2007-09-26 1:39 ` Mike Houston
2007-09-25 12:05 ` Rafael J. Wysocki
2007-09-25 12:05 ` Alexey Starikovskiy
2007-09-25 12:39 ` Rafael J. Wysocki
2007-09-25 12:53 ` Alexey Starikovskiy
2007-09-25 13:25 ` Rafael J. Wysocki
2007-09-25 13:15 ` Alexey Starikovskiy
2007-09-25 14:18 ` Rafael J. Wysocki
2007-09-25 14:19 ` Alexey Starikovskiy
2007-09-25 14:52 ` Rafael J. Wysocki [this message]
2007-09-25 14:45 ` Alexey Starikovskiy
2007-09-25 15:54 ` Rafael J. Wysocki
2007-09-25 16:23 ` Andrew Morton
2007-09-25 16:25 ` Alexey Starikovskiy
2007-09-25 11:25 ` Alexey Starikovskiy
2007-09-25 16:30 ` Torsten Kaiser
2007-09-25 16:31 ` Alexey Starikovskiy
2007-09-25 16:34 ` Alexey Starikovskiy
2007-09-25 15:40 ` Linus Torvalds
2007-09-25 16:00 ` Rafael J. Wysocki
2007-09-25 21:44 ` ACPI suspend/hibernate tests (was: ACPI power off regression in 2.6.23-rc8) Frans Pop
2007-09-25 22:18 ` Rafael J. Wysocki
2007-09-25 22:28 ` Frans Pop
2007-09-26 14:59 ` ACPI power off regression in 2.6.23-rc8 (NOT in rc7) Tim Post
-- strict thread matches above, loose matches on Subject: below --
2007-09-25 11:02 Daniel Ritz
2007-09-25 11:29 ` Alexey Starikovskiy
2007-09-25 12:03 ` Rafael J. Wysocki
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=200709251652.05589.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=astarikovskiy@suse.de \
--cc=aystarik@gmail.com \
--cc=damien.wyart@free.fr \
--cc=elendil@planet.nl \
--cc=just.for.lkml@googlemail.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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