From: Benjamin Herrenschmidt <benh@kernel.crashing.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: powerpc build failure
Date: Tue, 10 Jun 2008 17:20:09 +1000 [thread overview]
Message-ID: <1213082409.25745.28.camel@pasglop> (raw)
In-Reply-To: <20080610165441.a7c5ddd0.sfr@canb.auug.org.au>
On Tue, 2008-06-10 at 16:54 +1000, Stephen Rothwell wrote:
> Hi Paul,
>
> Today's linux-next tree build (powerpc ppc64_defconfig) failed like this:
>
> UPD include/linux/compile.h
> arch/powerpc/mm/built-in.o: In function `ht64_insert_pte':
> hash_native_64.c:(.text+0x4756): undefined reference to `_PAGE_HPTE_SUB0'
>
> I have reverted commit 2d9a973b0fee245af43b73412a08e88bc955644d
> ("powerpc: Free a PTE bit on ppc64 with 64K pages") for now.
Yup, that's the way to go. It's broken, I'll have to do things a bit
differently, I "forgot" our 64K SPU hack when using 4K pages assumes
we have the same PTE format :-( I'll have to implement a separate low
level asm function for hashing 64K pages on a 4K kernel.
Ben.
next prev parent reply other threads:[~2008-06-10 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 6:54 linux-next: powerpc build failure Stephen Rothwell
2008-06-10 7:20 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-11 9:27 Stephen Rothwell
2008-06-11 9:59 ` Ingo Molnar
2008-06-12 1:38 ` Paul Mackerras
2008-06-12 5:33 ` Alan Modra
2008-06-12 7:05 ` Stephen Rothwell
2008-06-12 7:16 ` Ingo Molnar
2008-06-12 7:27 ` Stephen Rothwell
2008-06-12 7:47 ` Ingo Molnar
2008-06-12 7:23 ` Benjamin Herrenschmidt
2008-06-12 7:24 ` Stephen Rothwell
2008-06-12 18:12 ` Sam Ravnborg
2008-06-12 8:15 ` Alan Modra
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=1213082409.25745.28.camel@pasglop \
--to=benh@kernel.crashing.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).