From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH] powerpc/kvm/booke: fix altivec related build break
Date: Wed, 2 May 2018 08:35:28 +0000 [thread overview]
Message-ID: <5AE9784E.7020304@nxp.com> (raw)
In-Reply-To: <874ljx5g6q.fsf@concordia.ellerman.id.au>
Hi Michael,
On 04/27/2018 09:14 AM, Michael Ellerman wrote:
> laurentiu.tudor@nxp.com writes:
>> From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
>>
>> Add missing "altivec unavailable" interrupt injection helper
>> thus fixing the linker error below:
>>
>> arch/powerpc/kvm/emulate_loadstore.o: In function `kvmppc_check_altivec_=
disabled':
>> arch/powerpc/kvm/emulate_loadstore.c: undefined reference to `.kvmppc_co=
re_queue_vec_unavail'
>>
>> Fixes: 09f984961c137c4b ("KVM: PPC: Book3S: Add MMIO emulation for VMX i=
nstructions")
>
> What config are you using to hit this? I'd like to add it to my
> auto-builder to catch it in future.
>
Start with the corenet64_smp_defconfig and enable CONFIG_KVM_E500MC=20
option found in "Virtualization -> KVM support for PowerPC=20
E500MC/E5500/E6500 processors".
P.S. Sorry for the late reply. I took advantage of labor day and=20
arranged a mini-vacation. :-)
---
Best Regards, Laurentiu=
next prev parent reply other threads:[~2018-05-02 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 12:33 [PATCH] powerpc/kvm/booke: fix altivec related build break laurentiu.tudor
2018-04-27 6:14 ` Michael Ellerman
2018-05-02 8:35 ` Laurentiu Tudor [this message]
2018-04-28 11:12 ` Michael Ellerman
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=5AE9784E.7020304@nxp.com \
--to=laurentiu.tudor@nxp.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.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).