RE: [PATCH RFC 0/5] Eliminate double-copying of FP/VMX/VSX state

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: kvm-owner@xxxxxxxxxxxxxxx [mailto:kvm-owner@xxxxxxxxxxxxxxx] On
> Behalf Of Paul Mackerras
> Sent: Wednesday, August 07, 2013 9:52 AM
> To: Alexander Graf; Benjamin Herrenschmidt
> Cc: kvm-ppc@xxxxxxxxxxxxxxx; kvm@xxxxxxxxxxxxxxx
> Subject: [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.

Nice work Paul! What do you suggest for KVM BookE AltiVec v2 patchset,
should I wait for this RFC or should I go ahead with the version based
on the existing infrastructure?

-Mike

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux