From: Bruce Majia <bruce.majia@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org, kvm-ppc <kvm-ppc@vger.kernel.org>,
Liu Yu <yu.liu@freescale.com>
Subject: Re: [PATCH] KVM: PPC: E500 compile fix
Date: Fri, 26 Mar 2010 15:15:19 +0800 [thread overview]
Message-ID: <20100326071519.GA24375@localhost> (raw)
In-Reply-To: <4B530B43.6070705@redhat.com>
On Sun, Jan 17, 2010 at 03:06:11PM +0200, Avi Kivity wrote:
> On 01/10/2010 07:01 PM, Alexander Graf wrote:
> > While trying to compile an E500 vmlinux, I stumbled across a compilation bug
> > that was obviously there before I touched any of the code. A trace point
> > doesn't get the correct arguments.
> >
> > Since that shouldn't be any critical to the functionality of the code, my quick
> > workaround is to #if 0 it out. I would very much appreciate someone fixing it
> > properly though.
> >
> > Liu, it would be nice if you could be the one doing that.
> >
>
> Applied, thanks.
Hi Avi,
Seems the problem still exists in the mainline kernel. Are you guys miss
something in the past few months? Does it means even if I passed compile
phase with the '#if 0' workaround, it's functions are not completed yet.
So its impossible to try kvm on ppc e500 target?
Thanks,
-bm
>
> --
> error compiling committee.c: too many arguments to function
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-26 7:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 17:01 [PATCH] KVM: PPC: E500 compile fix Alexander Graf
2010-01-11 7:05 ` Liu Yu-B13201
[not found] ` <0A1FE637C2C7E148B9573BB60CC630E56C3F14-bKEhWGtIRUJ4Lp7cDGe+DVjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2010-01-12 0:09 ` Alexander Graf
2010-01-17 13:06 ` Avi Kivity
2010-03-26 7:15 ` Bruce Majia [this message]
2010-03-26 9:10 ` Alexander Graf
[not found] ` <A306CC20-B0E4-4C6B-BAE4-A4F955E6663E-l3A5Bk7waGM@public.gmane.org>
2010-03-26 9:14 ` Liu Yu-B13201
2010-03-26 10:40 ` Bruce Majia
2010-03-26 10:50 ` Alexander Graf
[not found] ` <272B4229-9AC7-4D29-820F-5F958D4CC71C-l3A5Bk7waGM@public.gmane.org>
2010-03-26 11:20 ` Bruce Majia
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=20100326071519.GA24375@localhost \
--to=bruce.majia@gmail.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=yu.liu@freescale.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