linuxppc-dev.lists.ozlabs.org archive mirror
 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: Tue, 19 Mar 2013 17:16:31 -0500	[thread overview]
Message-ID: <1363731391.16671.32@snotra> (raw)
In-Reply-To: <1363728127.8336.39.camel@jlt4.sipsolutions.net> (from johannes@sipsolutions.net on Tue Mar 19 16:22:07 2013)

On 03/19/2013 04:22:07 PM, Johannes Berg wrote:
> On Tue, 2013-03-19 at 16:10 -0500, Scott Wood wrote:
>=20
> > > I was going to say I have no idea, but looking at it again ... =20
> this is
> > > in the *resume* code, not the suspend code as I'd assumed, and on
> > > resume
> > > I guess I felt it was safer to not assume it didn't change, since =20
> it
> > > could be a slightly different kernel that loaded and restored the
> > > hibernation image?
> >
> > Wouldn't that be doomed for other reasons?
>=20
> Most likely, yeah.
>=20
> > I wonder about kernel modules, though flushing 32 MiB wouldn't be
> > adequate there.
>=20
> Good question, but would they be running? You have to have 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 loading =20
all modules that were loaded before suspend (as they're normally not =20
swappable)?  I'm not too familiar with what gets saved where.

> > It's not a displacement flush (i.e. you don't do a separate load =20
> pass
> > first) -- it just flushes lines if they happen to be present, and
> > leaves alone anything outside that range.  Given that you just =20
> finished
> > copying a bunch of data, most likely what's in the cache is the last
> > bit of data you copied.
>=20
> Oops, good point.
>=20
> Maybe there's a way to completely flush the (i)cache? :-)

There is, but it's platform-dependent, and not pleasant on our chips =20
(need a displacement flush for L1, and sometimes errata are involved =20
for L2).

-Scott=

  reply	other threads:[~2013-03-19 22:16 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 [this message]
2013-03-22 10:58                 ` Johannes Berg
2013-03-22 22:14                   ` Scott Wood
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=1363731391.16671.32@snotra \
    --to=scottwood@freescale.com \
    --cc=dongsheng.wang@freescale.com \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@lists.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).