Skip to contentSkip to conversation

kvm ppc refactoring

RFC PATCH In review Hollis Blanchard 2 participants 3 messages Sep 29, 2008

lore
Share & tools
lore
#0 lore raw

RFC PATCH 1/1 kvm ppc refactoring

These patches refactor the KVM PPC code to support non-Book E processors. The Book E code might need a little more work to support e500, but probably not much. Beyond this, we still need to split struct kvm_vcpu_arch using container_of() macros.

There's a lot of code movement, so it might be easier to review by examining the final result. Basically we have powerpc.c and emulate.c calling core-specific functions, some of which are provided by booke.c and some by 44x*.c.

Comments?

-Hollis

#1 lore raw
Quoted 7 lines · Hollis Blanchard

These patches refactor the KVM PPC code to support non-Book E processors. The
Book E code might need a little more work to support e500, but probably not
much. Beyond this, we still need to split struct kvm_vcpu_arch using container_of() macros.

Quoted 8 lines

There's a lot of code movement, so it might be easier to review by examining
the final result. Basically we have powerpc.c and emulate.c calling core-specific functions, some of which are provided by booke.c and some by
44x*.c.

Comments?

Does non-Book E processors mean 97x series :-)?

Alex

#2 lore raw
In reply to Hollis Blanchard
Quoted 16 lines · Alexander Graf
Quoted 14 lines · Hollis Blanchard

These patches refactor the KVM PPC code to support non-Book E processors. The
Book E code might need a little more work to support e500, but probably not
much. Beyond this, we still need to split struct kvm_vcpu_arch using container_of() macros.

There's a lot of code movement, so it might be easier to review by examining
the final result. Basically we have powerpc.c and emulate.c calling core-specific functions, some of which are provided by booke.c and some by
44x*.c.

Quoted 3 lines
Quoted 1 line

Comments?

Does non-Book E processors mean 97x series :-)?

That's not something I'm personally looking at right now, but this patch series would get you closer. :)

Probably the most feasible would be to ignore 970's hypervisor mode (since you can't use it on any generally available platforms anyways), and implement 440-style software-only virtualization instead. I've heard people dreaming about doing exactly that for Cell (same problem).

If you want to chat about how exactly this could be implemented, I'd be happy to brainstorm with you... :)

Signature · 2 lines
Hollis Blanchard
IBM Linux Technology Center