From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Tim Abbott <tabbott@mit.edu>
Subject: Re: in_suspend and __nosave
Date: Fri, 1 May 2009 00:09:07 +0200 [thread overview]
Message-ID: <200905010009.07935.rjw@sisk.pl> (raw)
In-Reply-To: <20090430203000.GA10999@uranus.ravnborg.org>
On Thursday 30 April 2009, Sam Ravnborg wrote:
> Hi Rafael & Linus.
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.
>
> I understand that in_suspend is special as in that we do not
> want the value restored while resuming.
> But is there no other way to do so today?
On x86-64 we can probably get rid of it, a little code rework is needed for
this purpose. Unfortunately some more work is required to do the same
thing on x86-32.
> All I want is to kill a lot from the vmlinux.lds files.
Well, removing the __nosavedata is on my todo list, but not on the top of it.
> 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?
Yes, it is.
Thanks,
Rafael
next prev parent reply other threads:[~2009-04-30 22:09 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 [this message]
2009-05-03 21:57 ` Pavel Machek
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=200905010009.07935.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--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®