RFC Eliminate double-copying of FP/VMX/VSX state
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest5 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | powerpc: Put FP/VSX and VR state into structuresarch/ arch/ arch/ +14 more | +201 | 0 replies | |
| 2/5 | powerpc: Provide for giveup_fpu/altivec to save state in alternate locationarch/ arch/ arch/ +3 more | +48 | 0 replies | |
| 3/5 | KVM: PPC: Use load_fp/vr_state rather than load_up_fpu/altivecarch/ arch/ arch/ +3 more | +14 | 0 replies | |
| 4/5 | KVM: PPC: Store FP/VSX/VMX state in thread_fp/vr_state structuresarch/ arch/ arch/ +6 more | +131 | 0 replies | |
| 5/5 | KVM: PPC: Book3S: Load/save FP/VMX/VSX state directly to/from vcpu structarch/ arch/ arch/ | +19 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC 0/5] Eliminate double-copying of FP/VMX/VSX state
At present, PR KVM and BookE KVM does multiple copies of FP and related state because of the way that they use the arrays in the thread_struct as an intermediate staging post for the state. They do this so that they can use the existing system functions for loading and saving state, and so that they can keep guest state in the CPU registers while executing general kernel code.
This patch series reorganizes things so that KVM and the main kernel use the same representation for FP/VMX/VSX state, and so that guest state can be loaded/save directly from/to the vcpu struct instead of having to go via the thread_struct. This simplifies things and should be a little faster.
This series is against Alex Graf's kvm-ppc-queue branch plus my recent series of 23 patches to make PR and HV KVM coexist.
Paul.