From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
Paul Mackerras <paulus@samba.org>
Subject: Re: linux-next: kbuild tree build failure
Date: Mon, 7 Jul 2008 14:51:38 +0200 [thread overview]
Message-ID: <20080707125138.GA16569@uranus.ravnborg.org> (raw)
In-Reply-To: <20080707184038.aaeb8d40.sfr@canb.auug.org.au>
On Mon, Jul 07, 2008 at 06:40:38PM +1000, Stephen Rothwell wrote:
> Hi Sam,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> arch/powerpc/platforms/cell/spu_base.c: In function '__spu_trap_data_seg':
> arch/powerpc/platforms/cell/spu_base.c:194: error: duplicate case value
> arch/powerpc/platforms/cell/spu_base.c:177: error: previously used here
>
> This means that USER_REGION_ID (line 177) is the same as KERNEL_REGION_ID
> (line 194).
>
> From include/asm-powerpc/pgtable-ppc64.h:
>
> #define REGION_SHIFT 60UL
> #define REGION_MASK (0xfUL << REGION_SHIFT)
> #define REGION_ID(ea) (((unsigned long)(ea)) >> REGION_SHIFT)
>
> #define VMALLOC_REGION_ID (REGION_ID(VMALLOC_START))
> #define KERNEL_REGION_ID (REGION_ID(PAGE_OFFSET))
> #define VMEMMAP_REGION_ID (0xfUL)
> #define USER_REGION_ID (0UL)
>
> From include/asm-powerpc/page.h:
>
> #define PAGE_OFFSET ASM_CONST(CONFIG_PAGE_OFFSET)
>
> From .config:
>
> CONFIG_PAGE_OFFSET=0xffffffff
>
> Not good.
>
> From arch/powerpc/Kconfig (ADVANCED_OPTIONS is not set):
>
> config PAGE_OFFSET_BOOL
> bool "Set custom page offset address"
> depends on ADVANCED_OPTIONS
>
> config PAGE_OFFSET
> hex "Virtual address of memory base" if PAGE_OFFSET_BOOL
> default "0xc0000000"
>
> if PPC64
> config PAGE_OFFSET
> hex
> default "0xc000000000000000"
> endif
>
> Reverting commit 9ba4ff5059e1a26698786373c8c71321c37ef7f9 ("kconfig:
> normalize int/hex values") seems to have fixed it.
>
> From .config:
>
> CONFIG_PAGE_OFFSET=0xc000000000000000
I see what is wrong - we use a int to hold the value above
and it does not fit.
Will fix tonight or tomorrow.
Sam
next prev parent reply other threads:[~2008-07-07 12:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 8:40 linux-next: kbuild tree build failure Stephen Rothwell
2008-07-07 12:51 ` Sam Ravnborg [this message]
2008-07-07 13:08 ` Stephen Rothwell
2008-07-07 16:13 ` Roman Zippel
2008-07-07 21:01 ` Sam Ravnborg
2008-07-07 23:36 ` Michael Ellerman
2008-07-08 2:55 ` Roman Zippel
2008-07-10 0:51 ` Michael Ellerman
2008-07-10 14:59 ` Roman Zippel
2008-07-14 16:53 ` Milton Miller
2008-07-08 21:19 ` Sam Ravnborg
2008-07-10 14:52 ` Roman Zippel
2008-07-25 4:13 ` Stephen Rothwell
2008-07-26 10:06 ` Sam Ravnborg
2008-07-26 12:40 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-07-12 22:32 Milton Miller
2008-07-12 23:21 ` Roman Zippel
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=20080707125138.GA16569@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).