On 01.09.2010, at 14:09, 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.
Unfortunately all the interrupt magic is not cpu code. The qemu model is broken there. hw/ code just directly pokes env-> variables to trigger hard interrupts. Alex