From: Paul Mackerras <paulus@samba.org>
To: Alexander Graf <agraf@suse.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: [PATCH RFC 0/5] Eliminate double-copying of FP/VMX/VSX state
Date: Wed, 7 Aug 2013 16:52:20 +1000 [thread overview]
Message-ID: <20130807065220.GF31007@iris.ozlabs.ibm.com> (raw)
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.
next reply other threads:[~2013-08-07 6:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 6:52 Paul Mackerras [this message]
2013-08-07 6:53 ` [PATCH RFC 1/5] powerpc: Put FP/VSX and VR state into structures Paul Mackerras
2013-08-07 6:54 ` [PATCH RFC 2/5] powerpc: Provide for giveup_fpu/altivec to save state in alternate location Paul Mackerras
2013-08-07 6:54 ` [PATCH RFC 3/5] KVM: PPC: Use load_fp/vr_state rather than load_up_fpu/altivec Paul Mackerras
2013-08-07 6:55 ` [PATCH RFC 4/5] KVM: PPC: Store FP/VSX/VMX state in thread_fp/vr_state structures Paul Mackerras
2013-08-07 6:56 ` [PATCH RFC 5/5] KVM: PPC: Book3S: Load/save FP/VMX/VSX state directly to/from vcpu struct Paul Mackerras
2013-08-07 8:37 ` [PATCH RFC 0/5] Eliminate double-copying of FP/VMX/VSX state Caraman Mihai Claudiu-B02008
2013-08-08 12:08 ` Paul Mackerras
2013-08-08 12:50 ` Caraman Mihai Claudiu-B02008
2013-09-09 7:28 ` Michael Neuling
2013-09-09 8:12 ` Alexander Graf
2013-09-09 9:38 ` Michael Neuling
2013-09-09 9:44 ` Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130807065220.GF31007@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox