On 09/01/2010 03:09 PM, Avi Kivity wrote:
 On 09/01/2010 02:58 PM, Alexander Graf wrote:

Why not limit it to ppc?  Someone might call it by accident.
How would you model it? Call kvm_arch_set_interrupt in hw/ppc.c? Which header would I define the call in?


Well, eventually this finds its way to cpu code in target-ppc, no? from there you can call a function in target-ppc/kvm.c without any need for tricks.

So just hack it there.


Another way to look at this: shouldn't this be the same for kvm and non-kvm?

--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


Reply via email to