From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Blanchard <hollisb@us.ibm.com>,
Hollis@ozlabs.org, linuxppc-dev@ozlabs.org,
linux-next@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: testing (Was: Re: linux-next: scsi-post-merge tree build failure)
Date: Mon, 22 Dec 2008 20:52:36 -0500 [thread overview]
Message-ID: <20081223015236.GA7137@zod.rchland.ibm.com> (raw)
In-Reply-To: <20081223100456.bb556b19.sfr@canb.auug.org.au>
On Tue, Dec 23, 2008 at 10:04:56AM +1100, Stephen Rothwell wrote:
>Hi Ben,
>
>On Tue, 23 Dec 2008 07:56:32 +1100 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>>
>> On Tue, 2008-12-23 at 01:25 +1100, Stephen Rothwell wrote:
>> > Hi Paul, Ben,
>> >
>> > Today's linux-next build (powerpc ppc44x_config) failed like this:
>> >
>> > arch/powerpc/kvm/powerpc.c: In function 'kvm_arch_vcpu_put':
>> > arch/powerpc/kvm/powerpc.c:333: error: implicit declaration of function '_tlbil_all'
>> >
>> > Probably caused by commit 2a4aca1144394653269720ffbb5a325a77abd5fa
>> > ("powerpc/mm: Split low level tlb invalidate for nohash processors").
>> > Reverting just that commit was too difficult, so I have reverted the
>> > powerpc tree for today.
>>
>> You can't revert that without reverting my whole series.
>
>I know that ... I tried.
>
>> Adding a #include ../mm/mmu_decl.h to the kvm code should fix it for
>> now.
>>
>> I need to talk to hollis about the right way to do that stuff in
>> the long run but it might be it... those _tlbil things are low level
>> stuff that aren't supposed to be used by the outside world which is
>> why I moved the declarations there, but KVM is also low level :-)
>
>So, why is this series in powerpc/next at all if some of the modified
>files haven't even been compiled? A simple ppc44x_defconfig build of the
>powerpc/next tree fails - which I would have thought would be part of the
>testing since KVM is only implemented for 44x on powerpc.
Well, they were, and then they weren't. I tested this series starting
with the ppc44x_defconfig. However, I was incrementally compiling them
and I also had the 16/64K pages patch applied and 64K enabled. That
resulted in a kernel that was too big for the wrapper, so I went in
and turned some stuff off to make the kernel smaller. That included
the KVM stuff. By the time I was done building and testing the whole
series, it had remained disabled.
That might sound like a cop-out, but it's what happend. I should have
done a simple build after I was done. Sorry Stephen.
josh
prev parent reply other threads:[~2008-12-23 1:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 14:25 linux-next: scsi-post-merge tree build failure Stephen Rothwell
2008-12-22 14:51 ` Stephen Rothwell
2008-12-22 20:56 ` Benjamin Herrenschmidt
2008-12-22 23:04 ` testing (Was: Re: linux-next: scsi-post-merge tree build failure) Stephen Rothwell
2008-12-23 0:19 ` Benjamin Herrenschmidt
2008-12-23 1:52 ` Josh Boyer [this message]
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=20081223015236.GA7137@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=Hollis@ozlabs.org \
--cc=hollisb@us.ibm.com \
--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).