From: Dominik Dingel <dingel@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
Dominik Dingel <dingel@linux.vnet.ibm.com>,
Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PATCH] s390: Async page fault control
Date: Tue, 9 Jul 2013 17:47:45 +0200 [thread overview]
Message-ID: <1373384866-36233-1-git-send-email-dingel@linux.vnet.ibm.com> (raw)
Following the current discussion on the kvm ML, here are the qemu bits
regarding async page faults. They are responsible for enabling, disabling
the feature and adding a savevm handler for live migration.
Dominik Dingel (1):
Enable async page faults with live migration
target-s390x/kvm.c | 42 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
--
1.8.2.2
next reply other threads:[~2013-07-09 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 15:47 Dominik Dingel [this message]
2013-07-09 15:47 ` [Qemu-devel] [PATCH] Enable async page faults Dominik Dingel
2013-07-10 0:59 ` Andreas Färber
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=1373384866-36233-1-git-send-email-dingel@linux.vnet.ibm.com \
--to=dingel@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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;
as well as URLs for NNTP newsgroup(s).