From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Date: Fri, 04 Jul 2014 07:54:44 +0000 Subject: Re: [PATCH 5/6 v2] KVM: PPC: Book3E: Add ONE_REG AltiVec support Message-Id: <53B65DC4.5070001@suse.de> List-Id: References: <1404142497-6430-1-git-send-email-mihai.caraman@freescale.com> <1404142497-6430-6-git-send-email-mihai.caraman@freescale.com> <53B54DB2.1000805@suse.de> <92e31868b99a421ab578640527b41ccf@BY2PR03MB508.namprd03.prod.outlook.com> In-Reply-To: <92e31868b99a421ab578640527b41ccf@BY2PR03MB508.namprd03.prod.outlook.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "mihai.caraman@freescale.com" , "kvm-ppc@vger.kernel.org" Cc: "kvm@vger.kernel.org" , "linuxppc-dev@lists.ozlabs.org" On 03.07.14 18:11, mihai.caraman@freescale.com wrote: >> -----Original Message----- >> From: Alexander Graf [mailto:agraf@suse.de] >> Sent: Thursday, July 03, 2014 3:34 PM >> To: Caraman Mihai Claudiu-B02008; kvm-ppc@vger.kernel.org >> Cc: kvm@vger.kernel.org; linuxppc-dev@lists.ozlabs.org >> Subject: Re: [PATCH 5/6 v2] KVM: PPC: Book3E: Add ONE_REG AltiVec support >> >> >> On 30.06.14 17:34, Mihai Caraman wrote: >>> Add ONE_REG support for AltiVec on Book3E. >>> >>> Signed-off-by: Mihai Caraman >> Any chance we can handle these in generic code? > I expected this request :) Can we let this for a second phase to have > e6500 enabled first? I don't see the value of duplicating code in e500 specific code only to remove and combine it in common code in a follow-up patch after that. > Can you share with us a Book3S setup so I can validate the requested > changes? I already fell anxious touching strange hardware specific > Book3S code without running it. Until a few weeks ago I had an externally reachable G5 machine that we could've used for this. Unfortunately I had to replace the box with another one that's not quite as stable. I'll try and see if I can fix or replace it soon. Alex