From: Paul Mackerras <paulus@samba.org>
To: Alexander Graf <agraf@suse.de>
Cc: Suresh Warrier <warrier@linux.vnet.ibm.com>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [kvm-ppc:kvm-ppc-queue 7/9] ERROR: ".__spin_yield" [arch/powerpc/kvm/kvm.ko] undefined!
Date: Mon, 23 Mar 2015 14:00:40 +1100 [thread overview]
Message-ID: <20150323030040.GA8257@drongo> (raw)
In-Reply-To: <201503202053.m9p09BQr%fengguang.wu@intel.com>
On Fri, Mar 20, 2015 at 08:07:53PM +0800, kbuild test robot wrote:
> tree: git://github.com/agraf/linux-2.6.git kvm-ppc-queue
> head: 9b1daf3cfba1801768aa41b1b6ad0b653844241f
> commit: aba777f5ce0accb4c6a277e671de0330752954e8 [7/9] KVM: PPC: Book3S HV: Convert ICS mutex lock to spin lock
> config: powerpc-defconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout aba777f5ce0accb4c6a277e671de0330752954e8
> # save the attached .config to linux build tree
> make.cross ARCH=powerpc
>
> All error/warnings:
>
> >> ERROR: ".__spin_yield" [arch/powerpc/kvm/kvm.ko] undefined!
Yes, this is the patch that depends on the "powerpc: Export
__spin_yield" patch that Suresh posted to linuxppc-dev@ozlabs.org and
I acked.
I think the best thing at this stage is probably for Alex to take that
patch through his tree, assuming Michael is OK with that.
The patch is at https://patchwork.ozlabs.org/patch/443703/ or
https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-February/125315.html.
Alex, if you prefer me to post it to kvm-ppc@vger and kvm@vger, let me
know.
Paul.
next parent reply other threads:[~2015-03-23 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201503202053.m9p09BQr%fengguang.wu@intel.com>
2015-03-23 3:00 ` Paul Mackerras [this message]
2015-03-23 3:03 ` [kvm-ppc:kvm-ppc-queue 7/9] ERROR: ".__spin_yield" [arch/powerpc/kvm/kvm.ko] undefined! Michael Ellerman
2015-03-23 8:31 ` Alexander Graf
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=20150323030040.GA8257@drongo \
--to=paulus@samba.org \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=warrier@linux.vnet.ibm.com \
/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