From: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
To: Igor Mammedov <imammedo@redhat.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 1/3] sclp-s390: Add device to manage s390 memory hotplug
Date: Wed, 25 Jun 2014 11:16:43 -0400 [thread overview]
Message-ID: <53AAE7DB.6090409@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140625165345.62c04ba2@nial.usersys.redhat.com>
On 06/25/2014 10:53 AM, Igor Mammedov wrote:
> On Wed, 25 Jun 2014 10:26:58 -0400
> Matthew Rosato <mjrosato@linux.vnet.ibm.com> wrote:
>
>> Add sclpMemoryHotplugDev to contain associated data structures, etc.
>>
>> Signed-off-by: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
>> ---
>> hw/s390x/sclp.c | 30 ++++++++++++++++++++++++++++++
>> include/hw/s390x/sclp.h | 20 ++++++++++++++++++++
>> 2 files changed, 50 insertions(+)
>>
>> diff --git a/hw/s390x/sclp.c b/hw/s390x/sclp.c
>> index d8ddf35..769d7c3 100644
>> --- a/hw/s390x/sclp.c
>> +++ b/hw/s390x/sclp.c
>> @@ -183,3 +183,33 @@ void s390_sclp_init(void)
>> OBJECT(dev), NULL);
>> qdev_init_nofail(dev);
>> }
>> +
>> +sclpMemoryHotplugDev *init_sclp_memory_hotplug_dev(void)
>> +{
>> + DeviceState *dev;
>> + dev = qdev_create(NULL, TYPE_SCLP_MEMORY_HOTPLUG_DEV);
>> + object_property_add_child(qdev_get_machine(),
>> + TYPE_SCLP_MEMORY_HOTPLUG_DEV,
>> + OBJECT(dev), NULL);
>> + qdev_init_nofail(dev);
>> + return SCLP_MEMORY_HOTPLUG_DEV(object_resolve_path(
>> + TYPE_SCLP_MEMORY_HOTPLUG_DEV, NULL));
>> +}
>> +
>> +sclpMemoryHotplugDev *get_sclp_memory_hotplug_dev(void)
>> +{
>> + return SCLP_MEMORY_HOTPLUG_DEV(object_resolve_path(
>> + TYPE_SCLP_MEMORY_HOTPLUG_DEV, NULL));
>> +}
>> +
>> +static TypeInfo sclp_memory_hotplug_dev_info = {
>> + .name = TYPE_SCLP_MEMORY_HOTPLUG_DEV,
>> + .parent = TYPE_SYS_BUS_DEVICE,
>> + .instance_size = sizeof(sclpMemoryHotplugDev),
>
> Either parent above should be TYPE_DEVICE or
> s/DeviceState/SysBusDevice/ below
>
Oops, good catch - I tested s/DeviceState/SysBusDevice/ and will include
it in the next version. Thanks.
>> +struct sclpMemoryHotplugDev {
>> + DeviceState parent;
>
>
>
next prev parent reply other threads:[~2014-06-25 15:17 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 [this message]
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 ` [Qemu-devel] [PATCH v5 0/3] s390: Support for Hotplug of Standby Memory Igor Mammedov
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=53AAE7DB.6090409@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 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).