From: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org, borntraeger@de.ibm.com,
jan.kiszka@siemens.com, agraf@suse.de, jfrei@linux.vnet.ibm.com,
graalfs@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH 0/7] KVM regsync
Date: Fri, 21 Dec 2012 08:55:09 -0500 [thread overview]
Message-ID: <50D46A3D.4000009@linux.vnet.ibm.com> (raw)
Note: This is rework for the patch set previously submitted:
"s390/migration: Provide a cpu save for initial life migration work"
http://lists.nongnu.org/archive/html/qemu-devel/2012-11/msg02203.html
Rework the method used to synchronize CPU registers between Qemu &
KVM. This patch set extends kvm_arch_get_registers() to take a
register level parameter just like kvm_arch_put_registers does. All
existing code paths are updated to specify this new parameter.
Floating point register synchronization is added to
kvm_arch_[get,put]_registers().
--
-- Jason J. Herne (jjherne@linux.vnet.ibm.com)
next reply other threads:[~2012-12-21 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 13:55 Jason J. Herne [this message]
2013-01-03 13:57 ` [Qemu-devel] [PATCH 0/7] KVM regsync 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=50D46A3D.4000009@linux.vnet.ibm.com \
--to=jjherne@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=graalfs@linux.vnet.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.