From: Pavel Machek <pavel@ucw.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Tim Abbott <tabbott@MIT.EDU>
Subject: Re: in_suspend and __nosave
Date: Sun, 3 May 2009 23:57:09 +0200 [thread overview]
Message-ID: <20090503215709.GE1368@ucw.cz> (raw)
In-Reply-To: <20090430203000.GA10999@uranus.ravnborg.org>
Hi!
> While unifying vmlinux.lds for x86 I stumbled
> over the .data.nosave section.
>
> Searching a bit I found only a single user:
>
> swsusp.c:int in_suspend __nosavedata = 0;
>
> Do we really needs all this complexity for this single integer?
> We have this section defined in several arch lds files.
Well, original idea was that drivers may need some memory that's not
affected by hibernation/restore....
> It also occur to me that only: x86, powerpc, and sh
> implement pfn_is_nosave() which I think is the only
> place where we decide if we want to save a page or not.
>
> But we define the .data.nosave section in following
> architectures:
> arm, m32r, mips, mn10300, parisc, s390 in addition
> to the above archs that define pfn_is_nosave().
> Is this something to be cleaned up?
I guess people were just too happy with cut&paste. Ouch and someone
was working on arm hibernation, iIRC.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-05-03 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 20:30 Sam Ravnborg
2009-04-30 22:09 ` Rafael J. Wysocki
2009-05-03 21:57 ` 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=20090503215709.GE1368@ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sam@ravnborg.org \
--cc=tabbott@MIT.EDU \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®