From: Paul Mackerras <paulus@samba.org>
To: Caraman Mihai Claudiu-B02008 <B02008@freescale.com>
Cc: Alexander Graf <agraf@suse.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH RFC 0/5] Eliminate double-copying of FP/VMX/VSX state
Date: Thu, 8 Aug 2013 22:08:13 +1000 [thread overview]
Message-ID: <20130808120813.GB4865@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <300B73AA675FCE4A93EB4FC1D42459FF0A3161D0@039-SN2MPN1-012.039d.mgd.msft.net>
On Wed, Aug 07, 2013 at 08:37:24AM +0000, Caraman Mihai Claudiu-B02008 wrote:
>
> 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?
It's really up to you and whether you find that the changes I am
proposing would simplify your code. If they would, please tell Alex
once he's back. :)
Paul.
next prev parent reply other threads:[~2013-08-08 12:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 6:52 [PATCH RFC 0/5] Eliminate double-copying of FP/VMX/VSX state Paul Mackerras
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 [this message]
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=20130808120813.GB4865@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=B02008@freescale.com \
--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