All of lore.kernel.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: Tue, 19 Mar 2013 16:10:45 -0500	[thread overview]
Message-ID: <1363727445.16671.30@snotra> (raw)
In-Reply-To: <1363726534.8336.37.camel@jlt4.sipsolutions.net> (from johannes@sipsolutions.net on Tue Mar 19 15:55:34 2013)

On 03/19/2013 03:55:34 PM, Johannes Berg wrote:
> On Mon, 2013-03-18 at 17:12 -0500, Scott Wood wrote:
>=20
> > Could you elaborate on why book3s flushes the way it does?  What's
> > special about the first 32 MiB?  If it's to cover kernel code, why
> > would that be changing from what's already there?
>=20
> I was going to say I have no idea, but looking at it again ... this is
> in the *resume* code, not the suspend code as I'd assumed, and on =20
> resume
> I guess I felt it was safer to not assume it didn't change, since it
> could be a slightly different kernel that loaded and restored the
> hibernation image?

Wouldn't that be doomed for other reasons?

I wonder about kernel modules, though flushing 32 MiB wouldn't be =20
adequate there.

> It should be the same one, so I guess it should be
> exactly the same code, but I guess I wanted to make sure there wasn't
> anything weird there. As for why it'd be 32 MiB? No idea. Although =20
> that
> really ought to flush all your possible caches anyway, I guess.

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

-Scott=

  reply	other threads:[~2013-03-19 21:10 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 [this message]
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
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=1363727445.16671.30@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.