From: Pavel Machek <pavel@ucw.cz>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: myungjoo.ham@gmail.com,
Andreas Fenkart <andreas.fenkart@streamunlimited.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
kyungmin.park@samsung.com,
MyungJoo Ham <myungjoo.ham@samsung.com>,
linux-pm@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC][PATCH] ARM: Add initial hibernation support for Cortex A8 and A9
Date: Tue, 21 Dec 2010 20:51:06 +0100 [thread overview]
Message-ID: <20101221195105.GA29126@elf.ucw.cz> (raw)
In-Reply-To: <20101221145126.GU28157@n2100.arm.linux.org.uk>
Hi!
> The same should be true of things like perf.
>
> Things like the control register we already have the value cached, so
> there's little point saving another copy of it.
>
> What we should also have is a callback into the proc-*.S files for
> them to save the processor specific registers such as the TTB registers.
>
> And then, with non-secure mode, we run into issues about which registers
> we _can_ sanely read and write.
>
> What I'm saying is that rather than copying stuff verbatim from the
> ARM ARM, _think_ first and see what is actually necessary.
Well, the patch is not exactly nice, but "simple and stupid" version
that just saves everything might be useful baseline for bisect
etc... and speed should not really be issue here.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2010-12-21 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 5:43 [RFC][PATCH] ARM: Add initial hibernation support for Cortex A8 and A9 MyungJoo Ham
2010-12-21 14:41 ` Catalin Marinas
2010-12-21 14:41 ` Catalin Marinas
[not found] ` <AANLkTinFTAHzuEaLMn=xcevLCFvjga7RC6yztzC1fO5d@mail.gmail.com>
2010-12-21 14:51 ` Russell King - ARM Linux
[not found] ` <20101221145126.GU28157@n2100.arm.linux.org.uk>
2010-12-21 19:51 ` Pavel Machek [this message]
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=20101221195105.GA29126@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Hiroshi.DOYU@nokia.com \
--cc=andreas.fenkart@streamunlimited.com \
--cc=catalin.marinas@arm.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux@arm.linux.org.uk \
--cc=myungjoo.ham@gmail.com \
--cc=myungjoo.ham@samsung.com \
/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