public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale•com>
To: Johannes Berg <johannes@sipsolutions•net>
Cc: linuxppc-dev@lists•ozlabs.org,
	Wang Dongsheng <dongsheng.wang@freescale•com>
Subject: Re: [PATCH] powerpc: add Book E support to 64-bit hibernation
Date: Fri, 22 Mar 2013 17:14:50 -0500	[thread overview]
Message-ID: <1363990490.24790.12@snotra> (raw)
In-Reply-To: <1363949917.8238.25.camel@jlt4.sipsolutions.net> (from johannes@sipsolutions.net on Fri Mar 22 05:58:37 2013)

On 03/22/2013 05:58:37 AM, Johannes Berg wrote:
> On Tue, 2013-03-19 at 17:16 -0500, Scott Wood wrote:
>=20
> > > > I wonder about kernel modules, though flushing 32 MiB wouldn't =20
> be
> > > > adequate there.
> > >
> > > Good question, but would they be running? You have to have =20
> everything
> > > built in that you need to load the image? Or maybe not, with the
> > > userspace image restoration that became possible at some point...
> >
> > Is that all that's being restored in this step, or would we be =20
> loading
> > all modules that were loaded before suspend (as they're normally not
> > swappable)?  I'm not too familiar with what gets saved where.
>=20
> Yes, they would be restored since full memory is restored, but the
> kernel doing the restore hasn't typically had a chance to load =20
> modules.
> Although with uswsusp there probably are ways it can already have.

If we're loading executable code that wasn't there before[1], we need =20
to flush -- but there's no reason why modules would only be in the =20
lower 32 MiB.

-Scott

[1] within the resume process, not before suspend=

  reply	other threads:[~2013-03-22 22:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14  3:36 [PATCH] powerpc: add Book E support to 64-bit hibernation Wang Dongsheng
2013-03-14  8:37 ` Johannes Berg
2013-03-14 16:52   ` Scott Wood
2013-03-15 15:22     ` Johannes Berg
2013-03-18 22:12       ` Scott Wood
2013-03-19 20:55         ` Johannes Berg
2013-03-19 21:10           ` Scott Wood
2013-03-19 21:22             ` Johannes Berg
2013-03-19 22:16               ` Scott Wood
2013-03-22 10:58                 ` Johannes Berg
2013-03-22 22:14                   ` Scott Wood [this message]
2013-04-02  5:28                     ` Wang Dongsheng-B40534
2013-04-03  0:34                       ` Scott Wood
2013-04-03  5:36                         ` Wang Dongsheng-B40534
2013-04-03 20:15                           ` Scott Wood
2013-04-07  3:01                             ` Wang Dongsheng-B40534
2013-04-08 18:24                               ` Scott Wood

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=1363990490.24790.12@snotra \
    --to=scottwood@freescale$(echo .)com \
    --cc=dongsheng.wang@freescale$(echo .)com \
    --cc=johannes@sipsolutions$(echo .)net \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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