On 03.07.14 18:11, mihai.caraman@xxxxxxxxxxxxx wrote:
-----Original Message-----
From: Alexander Graf [mailto:agraf@xxxxxxx]
Sent: Thursday, July 03, 2014 3:34 PM
To: Caraman Mihai Claudiu-B02008; kvm-ppc@xxxxxxxxxxxxxxx
Cc: kvm@xxxxxxxxxxxxxxx; linuxppc-dev@xxxxxxxxxxxxxxxx
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 <mihai.caraman@xxxxxxxxxxxxx>
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
--
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
