From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] Fix __pfn_to_page(pfn) for CONFIG_DISCONTIGMEM=y
Date: Sat, 8 Nov 2008 14:12:21 +0100 [thread overview]
Message-ID: <200811081412.21736.rjw@sisk.pl> (raw)
In-Reply-To: <20081108125952.GB21405@elf.ucw.cz>
On Saturday, 8 of November 2008, Pavel Machek wrote:
> Hi!
>
> > This would be good to have in .28 IMO.
>
> Actually, this makes sense even for .27-stable, AFAICT.
Yes, it does, but it has to be merged first. :-)
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> > Subject: Fix __pfn_to_page(pfn) for CONFIG_DISCONTIGMEM=y
> >
> > Fix macro __pfn_to_page(pfn) so that it doesn't evaluate its
> > argument twice in the CONFIG_DISCONTIGMEM=y case, because 'pfn' may
> > be a result of a funtion call having side effects.
>
> function call?
Oh, I mean __pfn_to_page(a_function(something)), where a_function() does more
than just computing the result.
> > For example, the hibernation code applies pfn_to_page(pfn) to the
> > result of a function returning the pfn corresponding to the next set
> > bit in a bitmap and the current bit position is modified on each
> > call. This leads to "interesting" failures for CONFIG_DISCONTIGMEM=y
> > due to the current behavior of __pfn_to_page(pfn).
> >
> > Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> > Cc: Pavel Machek <pavel@suse.cz>
>
> Acked-by: Pavel Machek <pavel@suse.cz>
>
>
> > include/asm-generic/memory_model.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Index: linux-2.6/include/asm-generic/memory_model.h
> > ===================================================================
> > --- linux-2.6.orig/include/asm-generic/memory_model.h
> > +++ linux-2.6/include/asm-generic/memory_model.h
> > @@ -34,7 +34,7 @@
> >
> > #define __pfn_to_page(pfn) \
> > ({ unsigned long __pfn = (pfn); \
> > - unsigned long __nid = arch_pfn_to_nid(pfn); \
> > + unsigned long __nid = arch_pfn_to_nid(__pfn); \
> > NODE_DATA(__nid)->node_mem_map + arch_local_page_offset(__pfn, __nid);\
> > })
Thanks,
Rafael
next prev parent reply other threads:[~2008-11-08 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 12:53 Rafael J. Wysocki
2008-11-08 12:59 ` Pavel Machek
2008-11-08 13:12 ` Rafael J. Wysocki [this message]
2008-11-09 5:54 ` Andrew Morton
2008-11-09 11:37 ` Pavel Machek
2008-11-09 13:17 ` Rafael J. Wysocki
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=200811081412.21736.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@suse.cz \
--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®