From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Subject: Re: [PATCH] kvm/ppc/booke64: fix build breakage from Altivec, and disable e6500 Date: Fri, 10 May 2013 13:06:25 -0500 Message-ID: <1368209185.19683.4@snotra> References: <1368155698-15784-1-git-send-email-scottwood@freescale.com> <300B73AA675FCE4A93EB4FC1D42459FF3FE2FA@039-SN2MPN1-011.039d.mgd.msft.net> <0FD00883-6578-4AE0-A8A6-AAC6FD050870@suse.de> <300B73AA675FCE4A93EB4FC1D42459FF4059B5@039-SN2MPN1-013.039d.mgd.msft.net> <300B73AA675FCE4A93EB4FC1D42459FF407EBA@039-SN2MPN1-013.039d.mgd.msft.net> <300B73AA675FCE4A93EB4FC1D42459FF408017@039-SN2MPN1-013.039d.mgd.msft.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; delsp=Yes; format=Flowed Content-Transfer-Encoding: 8BIT Cc: Alexander Graf , Wood Scott-B07421 , "kvm-ppc@vger.kernel.org" , "kvm@vger.kernel.org" To: Caraman Mihai Claudiu-B02008 Return-path: In-Reply-To: <300B73AA675FCE4A93EB4FC1D42459FF408017@039-SN2MPN1-013.039d.mgd.msft.net> (from B02008@freescale.com on Fri May 10 13:03:27 2013) Content-Disposition: inline Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 05/10/2013 01:03:27 PM, Caraman Mihai Claudiu-B02008 wrote: > > -----Original Message----- > > From: kvm-ppc-owner@vger.kernel.org [mailto:kvm-ppc- > > owner@vger.kernel.org] On Behalf Of Alexander Graf > > Sent: Friday, May 10, 2013 7:51 PM > > To: Caraman Mihai Claudiu-B02008 > > Cc: Wood Scott-B07421; kvm-ppc@vger.kernel.org; kvm@vger.kernel.org > > Subject: Re: [PATCH] kvm/ppc/booke64: fix build breakage from > Altivec, > > and disable e6500 > > > > > > On 10.05.2013, at 18:50, Caraman Mihai Claudiu-B02008 wrote: > > > > >>> Do we really need to remove e6500 all together for this? > > >> > > >> No, just send real Altivec support quickly. We can add it to 3.10 > > through > > >> stable if it's too later, but I'd prefer to have it in within > the rc > > >> phase. > > > > > > I should have it by Monday, the smoke tests passed. > > > > Please make sure it also works on 32bit :) > > I can make sure that it doesn't break 32-bit. Altivec is not present > in > e500v2/e500mc/e5500 cores and e6500 is supported only by 64-bit host. > Are > you looking for G4 support? Just because Altivec isn't present on 32-bit doesn't mean that a particular patch can't break things there. Just as a patch to deal with lazy ee issues can break 32-bit, even though 32-bit doesn't have lazy ee. :-) -Scott