From: Wu Zhangjin <wuzhangjin@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH] MIPS: fix pfn_valid() for FLAGMEM
Date: Thu, 08 Oct 2009 18:57:43 +0800 [thread overview]
Message-ID: <1254999463.14496.29.camel@falcon> (raw)
In-Reply-To: <20091008103614.GA27323@elf.ucw.cz>
Hello,
> > >
> > > Looks mostly ok, small comments below.
> > >
> > > > @@ -168,13 +168,10 @@ typedef struct { unsigned long pgprot; } pgprot_t;
> > > >
> > > > #ifdef CONFIG_FLATMEM
> > > >
> > > > -#define pfn_valid(pfn) \
> > > > -({ \
> > > > - unsigned long __pfn = (pfn); \
> > > > - /* avoid <linux/bootmem.h> include hell */ \
> > > > - extern unsigned long min_low_pfn; \
> > > > - \
> > > > - __pfn >= min_low_pfn && __pfn < max_mapnr; \
> > > > +#define pfn_valid(pfn) \
> > > > +({ \
> > > > + extern int is_pfn_valid(unsigned long); \
> > > > + is_pfn_valid(pfn); \
> > > > })
> > >
> > > "extern int pfn_valid here"
> > >
> > > ...and get away without the ugly macro?
> > >
> >
> > Perhaps need to move the whole "#ifdef CONFIG_FLATMEM" to #ifndef
> > ASSEMBLY, otherwise,
> >
> > "arch/mips/include/asm/page.h:170: Error: unrecognized opcode `extern
> > int pfn_valid(unsigned long)'".
>
> I guess so. pfn_valid() will not work from assembly, anywa, so...
Seems pfn_valid() is only called in non-ASSEMBLY source code, so, we are
safe to move it to "#ifndef ASSEMBLY", just tested it, works.
Regards,
Wu Zhangjin
next prev parent reply other threads:[~2009-10-08 10:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 8:57 [PATCH] MIPS: fix pfn_valid() for FLAGMEM Wu Zhangjin
2009-10-08 9:29 ` Pavel Machek
2009-10-08 10:33 ` Wu Zhangjin
2009-10-08 10:36 ` Pavel Machek
2009-10-08 10:57 ` Wu Zhangjin [this message]
2009-10-08 9:58 ` Sergei Shtylyov
2009-10-08 10:36 ` Wu Zhangjin
2009-10-08 14:42 ` Ralf Baechle
2009-10-08 15:46 ` Wu Zhangjin
2009-10-08 18:50 ` Ralf Baechle
2009-10-09 15:43 ` Sergei Shtylyov
2009-10-09 15:48 ` Sergei Shtylyov
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=1254999463.14496.29.camel@falcon \
--to=wuzhangjin@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=pavel@ucw.cz \
--cc=ralf@linux-mips.org \
--cc=rjw@sisk.pl \
/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).