> -----Original Message----- > From: Paul Mackerras [mailto:paulus@xxxxxxxxx] > Sent: Thursday, August 08, 2013 3:08 PM > To: Caraman Mihai Claudiu-B02008 > Cc: Alexander Graf; Benjamin Herrenschmidt; kvm-ppc@xxxxxxxxxxxxxxx; > kvm@xxxxxxxxxxxxxxx > Subject: Re: [PATCH RFC 0/5] Eliminate double-copying of FP/VMX/VSX state > > On Wed, Aug 07, 2013 at 08:37:24AM +0000, Caraman Mihai Claudiu-B02008 > wrote: > > > > Nice work Paul! What do you suggest for KVM BookE AltiVec v2 patchset, > > should I wait for this RFC or should I go ahead with the version based > > on the existing infrastructure? > > It's really up to you and whether you find that the changes I am > proposing would simplify your code. If they would, please tell Alex > once he's back. :) I am not sure it simplifies the code. It's a more natural (and optimized) approach to have a common structure for kernel and KVM even though this implies touching lot of code. I don't like the idea to send the BookE AltiVec patchset just to be modified afterward but on the other hand e6500 core support depends on it and I would like to have it the next kernel release. As you suggested I would wait for Alex to comment on this. -Mike -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
