From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>, qemu-devel@nongnu.org
Cc: hangaohuai@huawei.com, lersek@redhat.com,
peter.huangpeng@huawei.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/5] qga: add three logical memory hotplug related commands
Date: Mon, 16 Feb 2015 20:05:03 -0600 [thread overview]
Message-ID: <20150217020503.13315.72635@loki> (raw)
In-Reply-To: <1421894406-12180-1-git-send-email-zhang.zhanghailiang@huawei.com>
Quoting zhanghailiang (2015-01-21 20:40:01)
> This patch series add three guest commands about memory block:
> guest-get-memory-blocks, guest-set-memory-blocks, guest-get-memory-block-size.
>
> With these three commands, we can get information about guest's memory block
> online/offline status and memory block size (unit of memory online/offline
> operation ). Also, we can change guest's memory block status (Logical memory
> hotplug/unplug) from host.
Thanks, applied to QGA tree:
https://github.com/mdroth/qemu/commits/qga
with a small change to patch 2 that replaces an assertion that the block
list isn't NULL with a reported error instead. This is more of an assertion
about the guest OS than the code itself, so it's best to avoid tying the
life-cycle of the agent to it. Otherwise looks good.
>
> Example of usage:
>
> {"execute":"guest-get-memory-blocks"}
> {"return":[{"online":true,"can-offline":false,"phys-index":0},{"online":true,"can-offline":true,"phys-index":1},{"online":true,"can-offline":false,"phys-index":2},{"online":true,"can-offline":false,"phys-index":3}]}
>
> {"execute":"guest-set-memory-blocks","arguments":{"mem-blks":[{"phys-index":0,"online":false},{"phys-index":1,"online":false},{"phys-index":3,"online":false}]}}
> {"return":[{"response":"operation-failed","error-code":22,"phys-index":0},{"response":"success","phys-index":1},{"response":"operation-failed","error-code":16,"phys-index":3}]}
>
> {"execute":"guest-get-memory-block-size"}
> {"return":134217728}
>
> v2:
> - Change return value of 'guest-set-memory-blocks' command from 'int' to a list
> of 'GuestMemoryBlockResponse', which contains more info about the operation
> results. It is suggested by Michael Roth. It is more useful for callers to
> know the exact operation result for each memory block, and also they can help
> callers to decide what to do next according to different error-code.
>
> zhanghailiang (5):
> qga: introduce three guest memory block commmands with stubs
> qga: implement qmp_guest_get_memory_blocks() for Linux with sysfs
> qga: implement qmp_guest_set_memory_blocks() for Linux with sysfs
> qga: implement qmp_guest_get_memory_block_size() for Linux with sysfs
> qga: add memory block command that unsupported to blacklist
>
> qga/commands-posix.c | 324 ++++++++++++++++++++++++++++++++++++++++++++++++++-
> qga/commands-win32.c | 21 ++++
> qga/qapi-schema.json | 114 ++++++++++++++++++
> 3 files changed, 458 insertions(+), 1 deletion(-)
>
> --
> 1.7.12.4
prev parent reply other threads:[~2015-02-17 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 2:40 [Qemu-devel] [PATCH v2 0/5] qga: add three logical memory hotplug related commands zhanghailiang
2015-01-22 2:40 ` [Qemu-devel] [PATCH v2 1/5] qga: introduce three guest memory block commmands with stubs zhanghailiang
2015-02-17 15:24 ` Eric Blake
2015-01-22 2:40 ` [Qemu-devel] [PATCH v2 2/5] qga: implement qmp_guest_get_memory_blocks() for Linux with sysfs zhanghailiang
2015-01-22 2:40 ` [Qemu-devel] [PATCH v2 3/5] qga: implement qmp_guest_set_memory_blocks() " zhanghailiang
2015-01-22 2:40 ` [Qemu-devel] [PATCH v2 4/5] qga: implement qmp_guest_get_memory_block_size() " zhanghailiang
2015-01-22 2:40 ` [Qemu-devel] [PATCH v2 5/5] qga: add memory block command that unsupported to blacklist zhanghailiang
2015-02-12 8:27 ` [Qemu-devel] [PATCH v2 0/5] qga: add three logical memory hotplug related commands zhanghailiang
2015-02-17 2:05 ` Michael Roth [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=20150217020503.13315.72635@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=hangaohuai@huawei.com \
--cc=lcapitulino@redhat.com \
--cc=lersek@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=zhang.zhanghailiang@huawei.com \
/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).