On 10.05.2013, at 20:06, Scott Wood wrote: > On 05/10/2013 01:03:27 PM, Caraman Mihai Claudiu-B02008 wrote: >> > -----Original Message----- >> > From: kvm-ppc-owner@xxxxxxxxxxxxxxx [mailto:kvm-ppc- >> > owner@xxxxxxxxxxxxxxx] On Behalf Of Alexander Graf >> > Sent: Friday, May 10, 2013 7:51 PM >> > To: Caraman Mihai Claudiu-B02008 >> > Cc: Wood Scott-B07421; kvm-ppc@xxxxxxxxxxxxxxx; kvm@xxxxxxxxxxxxxxx >> > 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. :-) Yeah, that's what I was referring to :). G4s use a different code path altogether and already work with Altivec for years. I doubt you'll manage to break anything there :). So what you should ensure is 1) 32bit e500 still compiles 2) 32bit e500 still executes fine, albeit without altivec Alex -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
