From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v5] ARM hibernation / suspend-to-disk (fwd)
Date: Wed, 29 Jun 2011 21:08:20 +0100 [thread overview]
Message-ID: <20110629200820.GC12421@e102144-lin.cambridge.arm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1106291555330.2266@localhost6.localdomain6>
Hi Frank,
On Wed, Jun 29, 2011 at 04:14:23PM +0100, Frank Hofmann wrote:
> Have you seen Will Deacon's suggested kexec changes ? That keeps a "reset
> stack" page around, _elsewhere_, and I've been considering using that. In
> the end, all swsusp_arch_resume() really requires is a stack page that's
> guaranteed to be outside the target kernel data, thereby left alone by the
> restore. __nosavedata is merely one way.
For what it's worth, in v4 of that series (hopefully I'll post it soon)
I'm starting to think about SMP kexec which necessitates that the reserved
stack page is placed in a fixed location. I'm planning to memblock_reserve
the page immediately below swapper for this.
Will
next prev parent reply other threads:[~2011-06-29 20:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 12:04 [RFC PATCH v5] ARM hibernation / suspend-to-disk (fwd) Frank Hofmann
2011-06-13 12:26 ` Russell King - ARM Linux
2011-06-13 12:40 ` Frank Hofmann
2011-06-13 13:20 ` Frank Hofmann
2011-06-13 13:56 ` Dave Martin
2011-06-13 15:34 ` Frank Hofmann
2011-06-13 16:11 ` Frank Hofmann
2011-06-13 16:44 ` Russell King - ARM Linux
2011-06-15 13:35 ` Frank Hofmann
2011-06-16 21:31 ` Russell King - ARM Linux
2011-06-20 12:32 ` Frank Hofmann
2011-06-21 14:35 ` Russell King - ARM Linux
2011-06-29 14:52 ` Matthieu CASTET
2011-06-29 15:14 ` Frank Hofmann
2011-06-29 20:08 ` Will Deacon [this message]
2011-07-05 12:37 ` Matthieu CASTET
[not found] ` <2C577202CB5719438D4E9608C565CB2C01B69D7F@NL-EXC-07.intra.local>
2011-07-05 17:09 ` Matthieu CASTET
2011-09-30 7:48 ` Barry Song
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=20110629200820.GC12421@e102144-lin.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).