linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/5] powerpc: fix suspend states again
Date: Mon, 19 Mar 2007 15:48:47 +0100	[thread overview]
Message-ID: <1174315727.5044.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20070319105358.796834000@sipsolutions.net>

On Mon, 2007-03-19 at 11:53 +0100, Johannes Berg wrote:
> plain text document attachment (002-fix-powermac-suspend-again.patch)
> In commit 0fba3a1f39f8b0a50b56c8b068fa52131cbc84c2 (a very long time ago,
> May 2006), I fixed a bug that caused powermacs to crash when you tried
> entering standby/mem suspend states.
> 
> As I'm now getting more familiar with the suspend code I notice a few
> more things:
>  1. we previously misunderstood what pm_ops is for, it isn't supposed to be
>     for doing platform dependent suspend/resume stuff that needs to be done
>     for suspend to disk (as we currently try to use it!), it is instead for
>     entering platform dependent suspend states ("standby", "mem").
>  2. due to the first point, we never properly save FPU and altivec states
>     when suspending to disk. It probably hasn't hurt yet because the process
>     that writes the "disk" to /sys/power/state uses neither and its context
>     is used.
> 
> This patch addresses these points as follows:
>  1. remove all pm_ops from powermac, powermac suspend to ram isn't currently
>     usable via /sys/power/state but is done via the PMU instead.
>  2. move the code responsible for storing FPU/altivec state into a new
>     arch_prepare_suspend function (previously, this was only present for
>     32-bit platforms from asm-ppc.)
> 
> A follow-on patch will create new pm_ops for via-pmu.
> 
> I removed
> 	set_context(current->active_mm->context.id, current->active_mm->pgd);
> because
>  1. it works without and
>  2. I don't see the point

No, you need that to restore the segment registers. I might work for you
by mere luck.

Ben.

  reply	other threads:[~2007-03-19 14:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 10:53 [PATCH 0/5] powermac suspend fixes Johannes Berg
2007-03-19 10:53 ` [PATCH 1/5] powerpc: generic time suspend/resume code Johannes Berg
2007-03-19 14:47   ` Benjamin Herrenschmidt
2007-03-19 21:51     ` Guennadi Liakhovetski
2007-03-19 22:11       ` Johannes Berg
2007-03-19 23:21         ` Guennadi Liakhovetski
2007-03-21 20:47       ` David Brownell
2007-03-21 22:48         ` Guennadi Liakhovetski
2007-05-02  5:02   ` Michael Ellerman
2007-05-02  8:25     ` Johannes Berg
2007-05-02 11:06       ` Michael Ellerman
2007-05-02 14:04         ` Johannes Berg
2007-03-19 10:53 ` [PATCH 2/5] powerpc: fix suspend states again Johannes Berg
2007-03-19 14:48   ` Benjamin Herrenschmidt [this message]
2007-03-19 15:22     ` Johannes Berg
2007-03-19 15:32       ` Benjamin Herrenschmidt
2007-03-19 15:45         ` Johannes Berg
2007-03-19 15:54           ` Johannes Berg
2007-03-19 16:22             ` Johannes Berg
2007-03-19 16:39               ` Benjamin Herrenschmidt
2007-03-19 16:06   ` Benjamin Herrenschmidt
2007-03-19 10:53 ` [PATCH 3/5] powermac: disallow pmu sleep notifiers from aborting sleep Johannes Berg
2007-03-19 14:49   ` Benjamin Herrenschmidt
2007-03-19 10:53 ` [PATCH 4/5] powermac: proper sleep management Johannes Berg
2007-03-19 14:50   ` Benjamin Herrenschmidt
2007-03-19 15:16     ` Johannes Berg
2007-03-19 23:44   ` Johannes Berg
2007-03-20  0:11     ` [PATCH 4/5 v2] " Johannes Berg
2007-03-20  0:48       ` Johannes Berg
2007-03-20  2:19         ` Johannes Berg
2007-03-19 10:53 ` [PATCH 5/5] remove dead code in via-pmu68k Johannes Berg
2007-03-19 19:17   ` Brad Boyer

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=1174315727.5044.6.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).