I don't know that kvm_ppc.c is a very information name for this sort
of
stuff. Since this is really host specific, not target specific, why
not
move it out of target-ppc.
I could combine kvm_ppc.c into target-ppc/kvm.c. However, they're
really
two different things, and I thought it would cause the least confusion
if they were logically separate. Most of it is hooks required by
common
code, and then some of it isn't. (I'm thinking about e.g. IA64 doing a
copy/paste, and then wondering which functions they actually need to
implement.) Regardless, I will still need a kvm_ppc.h, so kvm_ppc.c
seemed like a good place to match.