From: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: agraf@suse.de, borntraeger@de.ibm.com, aliguori@amazon.com,
imammedo@redhat.com, cornelia.huck@de.ibm.com,
pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v6 0/3] s390: Support for Hotplug of Standby Memory
Date: Wed, 16 Jul 2014 16:02:35 -0400 [thread overview]
Message-ID: <53C6DA5B.8090802@linux.vnet.ibm.com> (raw)
In-Reply-To: <1404136833-18500-1-git-send-email-mjrosato@linux.vnet.ibm.com>
On 06/30/2014 10:00 AM, Matthew Rosato wrote:
> This patchset adds support in s390 for a pool of standby memory,
> which can be set online/offline by the guest (ie, via chmem).
> The standby pool of memory is allocated as the difference between
> the initial memory setting and the maxmem setting.
> As part of this work, additional results are provided for the
> Read SCP Information SCLP, and new implentation is added for the
> Read Storage Element Information, Attach Storage Element,
> Assign Storage and Unassign Storage SCLPs, which enables the s390
> guest to manipulate the standby memory pool.
>
> This patchset is based on work originally done by Jeng-Fang (Nick)
> Wang.
>
> Sample qemu command snippet:
>
> qemu -machine s390-ccw-virtio -m 1024M,maxmem=2048M,slots=32 -enable-kvm
>
> This will allocate 1024M of active memory, and another 1024M
> of standby memory. Example output from s390-tools lsmem:
> =============================================================================
> 0x0000000000000000-0x000000000fffffff 256 online no 0-127
> 0x0000000010000000-0x000000001fffffff 256 online yes 128-255
> 0x0000000020000000-0x000000003fffffff 512 online no 256-511
> 0x0000000040000000-0x000000007fffffff 1024 offline - 512-1023
>
> Memory device size : 2 MB
> Memory block size : 256 MB
> Total online memory : 1024 MB
> Total offline memory: 1024 MB
>
>
> The guest can dynamically enable part or all of the standby pool
> via the s390-tools chmem, for example:
>
> chmem -e 512M
>
> And can attempt to dynamically disable:
>
> chmem -d 512M
>
Ping...
>
> Changes for v6:
> * Fix in sclp.h - DeviceState parent --> SysBusDevice parent
> in struct sclpMemoryHotplugDev.
> * Fix in assign_storage - int this_subregion_size, should
> be uint64_t.
> * Added information on how to test in the cover letter.
>
> Changes for v5:
> * Since ACPI memory hotplug is now in, removed Igor's patches
> from this set.
> * Updated sclp.c to use object_resolve_path() instead of
> object_property_find().
>
> Changes for v4:
> * Remove initialization code from get_sclp_memory_hotplug_dev()
> and place in its own function, init_sclp_memory_hotplug_dev().
> * Add hit to qemu-options.hx to note the fact that the memory
> size specified via -m might be forced to a boundary.
> * Account for the legacy s390 machine, which does not support
> memory hotplug.
> * Fix a bug in sclp.c - Change memory hotplug device parent to
> sysbus.
> * Pulled latest version of Igor's patch.
>
> Matthew Rosato (3):
> sclp-s390: Add device to manage s390 memory hotplug
> virtio-ccw: Include standby memory when calculating storage increment
> sclp-s390: Add memory hotplug SCLPs
>
> hw/s390x/s390-virtio-ccw.c | 46 +++++--
> hw/s390x/sclp.c | 289 +++++++++++++++++++++++++++++++++++++++++++-
> include/hw/s390x/sclp.h | 20 +++
> qemu-options.hx | 3 +-
> target-s390x/cpu.h | 18 +++
> target-s390x/kvm.c | 5 +
> 6 files changed, 366 insertions(+), 15 deletions(-)
>
prev parent reply other threads:[~2014-07-16 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 14:00 [Qemu-devel] [PATCH v6 0/3] s390: Support for Hotplug of Standby Memory Matthew Rosato
2014-06-30 14:00 ` [Qemu-devel] [PATCH v6 1/3] sclp-s390: Add device to manage s390 memory hotplug Matthew Rosato
2014-06-30 14:00 ` [Qemu-devel] [PATCH v6 2/3] virtio-ccw: Include standby memory when calculating storage increment Matthew Rosato
2014-06-30 14:00 ` [Qemu-devel] [PATCH v6 3/3] sclp-s390: Add memory hotplug SCLPs Matthew Rosato
2014-07-29 12:17 ` Christian Borntraeger
2014-07-29 14:53 ` Matthew Rosato
2014-07-16 20:02 ` Matthew Rosato [this message]
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=53C6DA5B.8090802@linux.vnet.ibm.com \
--to=mjrosato@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.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 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.