From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: qemu-devel@nongnu.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
borntraeger@de.ibm.com, jfrei@linux.vnet.ibm.com, agraf@suse.de,
jjherne@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH for-2.5 0/8] s390x: storage key migration
Date: Mon, 20 Jul 2015 15:49:50 +0200 [thread overview]
Message-ID: <1437400198-25382-1-git-send-email-cornelia.huck@de.ibm.com> (raw)
Here's the first batch of s390x patches I plan to send for 2.5.
This one deals with storage keys, which may be set by guests and
lacked a proper resting place so far. Introducing a device (that
is backed by the KVM_S390_{SET,GET}_SKEYS ioctls in the kvm case)
allows us to migrate them properly.
Also available as a branch on
git://github.com/cohuck/qemu s390-skey
Cornelia Huck (1):
s390x: add 2.5 compat s390-ccw-virtio machine
Jason J. Herne (7):
s390x: Create QOM device for s390 storage keys
s390x: Enable new s390-storage-keys device
s390x: Dump storage keys qmp command
s390x: Dump-skeys hmp support
s390x: Info skeys sub-command
s390x: Migrate guest storage keys (initial memory only)
s390x: Disable storage key migration on old machine type
MAINTAINERS | 1 +
hmp-commands.hx | 18 ++
hw/s390x/Makefile.objs | 2 +
hw/s390x/s390-skeys-kvm.c | 75 ++++++++
hw/s390x/s390-skeys.c | 402 ++++++++++++++++++++++++++++++++++++++++
hw/s390x/s390-virtio-ccw.c | 38 +++-
hw/s390x/s390-virtio.c | 11 +-
hw/s390x/s390-virtio.h | 2 +-
include/hw/s390x/storage-keys.h | 60 ++++++
monitor.c | 20 ++
qapi-schema.json | 13 ++
qmp-commands.hx | 25 +++
target-s390x/cpu.h | 2 -
target-s390x/mem_helper.c | 46 ++++-
target-s390x/mmu_helper.c | 28 ++-
trace-events | 4 +
16 files changed, 722 insertions(+), 25 deletions(-)
create mode 100644 hw/s390x/s390-skeys-kvm.c
create mode 100644 hw/s390x/s390-skeys.c
create mode 100644 include/hw/s390x/storage-keys.h
--
2.4.6
next reply other threads:[~2015-07-20 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 13:49 Cornelia Huck [this message]
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 1/8] s390x: add 2.5 compat s390-ccw-virtio machine Cornelia Huck
2015-07-20 13:58 ` Christian Borntraeger
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 2/8] s390x: Create QOM device for s390 storage keys Cornelia Huck
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 3/8] s390x: Enable new s390-storage-keys device Cornelia Huck
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 4/8] s390x: Dump storage keys qmp command Cornelia Huck
2015-07-20 14:32 ` Eric Blake
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 5/8] s390x: Dump-skeys hmp support Cornelia Huck
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 6/8] s390x: Info skeys sub-command Cornelia Huck
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 7/8] s390x: Migrate guest storage keys (initial memory only) Cornelia Huck
2015-07-21 8:08 ` Thomas Huth
2015-07-21 10:37 ` David Hildenbrand
2015-07-30 15:00 ` Jason J. Herne
2015-07-30 15:12 ` Thomas Huth
2015-08-13 14:11 ` Jason J. Herne
2015-08-13 15:44 ` Christian Borntraeger
2015-07-20 13:49 ` [Qemu-devel] [PATCH for-2.5 8/8] s390x: Disable storage key migration on old machine type Cornelia Huck
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=1437400198-25382-1-git-send-email-cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=jjherne@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 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).