From: Yang Rui Rui <ruirui.r.yang@tieto.com>
To: Yang Ruirui R <ruirui.r.yang@tietoenator.com>
Cc: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: ppc32 build failed
Date: Fri, 19 Nov 2010 14:58:05 +0800 [thread overview]
Message-ID: <4CE61FFD.3090807@tieto.com> (raw)
In-Reply-To: <4CE61B3D.3050906@tieto.com>
On 11/19/2010 02:37 PM, Yang Ruirui R wrote:
> On 11/19/2010 02:24 PM, Takuya Yoshikawa wrote:
>> (2010/11/19 15:01), Yang Rui Rui wrote:
>>> Hi,
>>>
>>> I searched the archive found some discutions about this, not fixed yet?
>>> could someone tell, is g4 kvm available now?
>>
>> Hi, (added kvm-ppc to Cc)
>>
>> I'm using g4 (Mac mini box) to run KVM.
>> - though not tried 2.6.37-rc2 yet.
>>
>> Aren't you using upstream qemu?
>> IIRC, ppc kvm needs to use upstream qemu.
>
> I use qemu-kvm git version. Do you means qemu instead of qemu-kvm?
Hi, qemu 0.13.0 build passed
>
>>
>>
>> You can see useful information on KVM "PowerPC port" page.
>> http://www.linux-kvm.org/page/PowerPC
>>
>> -> no g4 example but we can find enough information.
>>
>>
>> BTW, why the entry "Book3S PPC32" in the processor support table
>> is still "NO", anyone?
>> http://www.linux-kvm.org/page/Processor_support
>>
>
> Thanks a lot
>
>>
>> I don't know well about PPC, so you need to ask Alex about
>> more technical issues.
>>
>>
>> Takuya
>>
>>
>>>
>>> powerpc g4 build failed (host kernel 2.6.37-rc2):
>>>
>>> CC ppc-softmmu/kvm.o
>>> /home/dave/qemu-kvm/target-ppc/kvm.c: In function 'kvm_arch_init_vcpu':
>>> /home/dave/qemu-kvm/target-ppc/kvm.c:81: error: 'struct kvm_sregs' has no member named 'pvr'
>>> /home/dave/qemu-kvm/target-ppc/kvm.c: In function 'kvm_arch_get_registers':
>>> /home/dave/qemu-kvm/target-ppc/kvm.c:168: error: 'struct kvm_sregs' has no member named 'u'
>>> /home/dave/qemu-kvm/target-ppc/kvm.c:180: error: 'struct kvm_sregs' has no member named 'u'
>>> /home/dave/qemu-kvm/target-ppc/kvm.c:185: error: 'struct kvm_sregs' has no member named 'u'
>>> /home/dave/qemu-kvm/target-ppc/kvm.c:186: error: 'struct kvm_sregs' has no member named 'u'
>>> /home/dave/qemu-kvm/target-ppc/kvm.c:187: error: 'struct kvm_sregs' has no member named 'u'
>>> /home/dave/qemu-kvm/target-ppc/kvm.c:188: error: 'struct kvm_sregs' has no member named 'u'
>>> /home/dave/qemu-kvm/target-ppc/kvm.c: At top level:
>>> /home/dave/qemu-kvm/target-ppc/kvm.c:261: error: conflicting types for 'kvm_arch_process_irqchip_events'
>>> /home/dave/qemu-kvm/qemu-kvm.h:692: error: previous declaration of 'kvm_arch_process_irqchip_events' was here
>>> make[1]: *** [kvm.o] Error 1
>>> make: *** [subdir-ppc-softmmu] Error 2
>>>
>>
>
>
--
To adhere means to yield. To yield means to adhere.
next prev parent reply other threads:[~2010-11-19 6:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 6:01 ppc32 build failed Yang Rui Rui
[not found] ` <4CE612D0.4010508-++hxYGjEMp0AvxtiuMwx3w@public.gmane.org>
2010-11-19 6:24 ` Takuya Yoshikawa
[not found] ` <4CE61829.7060403-gVGce1chcLdL9jVzuh4AOg@public.gmane.org>
2010-11-19 6:37 ` Yang Rui Rui
2010-11-19 6:58 ` Yang Rui Rui [this message]
[not found] ` <4CE61FFD.3090807-++hxYGjEMp0AvxtiuMwx3w@public.gmane.org>
2010-11-19 7:04 ` Takuya Yoshikawa
2010-11-19 13:01 ` 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=4CE61FFD.3090807@tieto.com \
--to=ruirui.r.yang@tieto.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=ruirui.r.yang@tietoenator.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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