From: Igor Mammedov <imammedo@redhat.com>
To: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, agraf@suse.de, borntraeger@de.ibm.com,
aliguori@amazon.com, cornelia.huck@de.ibm.com,
pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v5 0/3] s390: Support for Hotplug of Standby Memory
Date: Fri, 27 Jun 2014 11:07:05 +0200 [thread overview]
Message-ID: <20140627110705.00256804@nial.usersys.redhat.com> (raw)
In-Reply-To: <1403706420-20109-1-git-send-email-mjrosato@linux.vnet.ibm.com>
On Wed, 25 Jun 2014 10:26:57 -0400
Matthew Rosato <mjrosato@linux.vnet.ibm.com> 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.
Could you add short description how to test it, please.
>
> 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-06-27 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 14:26 [Qemu-devel] [PATCH v5 0/3] s390: Support for Hotplug of Standby Memory Matthew Rosato
2014-06-25 14:26 ` [Qemu-devel] [PATCH v5 1/3] sclp-s390: Add device to manage s390 memory hotplug Matthew Rosato
2014-06-25 14:53 ` Igor Mammedov
2014-06-25 15:16 ` Matthew Rosato
2014-06-25 14:26 ` [Qemu-devel] [PATCH v5 2/3] virtio-ccw: Include standby memory when calculating storage increment Matthew Rosato
2014-06-25 14:27 ` [Qemu-devel] [PATCH v5 3/3] sclp-s390: Add memory hotplug SCLPs Matthew Rosato
2014-06-26 13:14 ` Christian Borntraeger
2014-06-26 15:30 ` Matthew Rosato
2014-06-27 9:07 ` Igor Mammedov [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=20140627110705.00256804@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=mjrosato@linux.vnet.ibm.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 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).