> -----Original Message----- > From: Alexander Graf [mailto:ag...@suse.de] > Sent: Friday, March 26, 2010 5:10 PM > To: Bruce Majia > Cc: Avi Kivity; kvm@vger.kernel.org; kvm-ppc; Liu Yu-B13201 > Subject: Re: [PATCH] KVM: PPC: E500 compile fix > > > On 26.03.2010, at 08:15, Bruce Majia wrote: > > > 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? > > If #if 0 only affects you if you want to trace that specific > function. It's probably safe to say you don't care, so just > #if 0 it out and be good :-). >
The trace info here is not that important. And will be removed in future patches... -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
