From: David Hildenbrand <david@redhat.com>
To: Vadim Galitsyn <vadim.galitsyn@profitbricks.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Cc: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>,
Mohammed Gamal <mohammed.gamal@profitbricks.com>,
Eduardo Otubo <eduardo.otubo@profitbricks.com>
Subject: Re: [Qemu-devel] [PATCH] hmp, qmp: introduce "info memory" and "query-memory" commands
Date: Mon, 19 Jun 2017 09:47:51 +0200 [thread overview]
Message-ID: <5c8dbd37-073c-28a8-0062-272c6df02373@redhat.com> (raw)
In-Reply-To: <20170613125515.30416-2-vadim.galitsyn@profitbricks.com>
On 13.06.2017 14:55, Vadim Galitsyn wrote:
> Commands above provide the following memory information in bytes:
Is the idea to have something like hmp_info_numa() ("info NUMA"), just
for qmp? And so it also works without NUMA?
I think, for this command to be helpful, you should include a per-NUMA
node information.
So what you could do:
- total_base memory
- total hotplugged memory
- base_memory per NUMA node
- hotplugged memory per NUMA node
>
> * hot-plug-memory - amount of memory that was hot-plugged.
>
We also have query-memory-devices for that already.
> * ballooned-actual-memory - size of the memory that remains
> available to the guest after ballooning, as reported by the
> guest. If the guest has not reported its memory, this value
> equals to @base-memory + @hot-plug-memory. If ballooning
> is not enabled, zero value is reported.
I don't think ballooning belongs into this at all.
>
> NOTE:
>
> Parameter @ballooned-actual-memory reports the same as
> "info balloon" command when ballooning is enabled. The idea
> to have it in scope of this command(s) comes from
> https://lists.gnu.org/archive/html/qemu-devel/2012-07/msg01472.html.
Can't you simply change query-balloon to show 0 in case no balloon is
around? Or why can't your caller simply deal with the fact that querying
the balloon might fail? Making a qmp interface directly copy the data
from another qmp interface looks strange.
>
> Signed-off-by: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>
> Signed-off-by: Mohammed Gamal <mohammed.gamal@profitbricks.com>
> Signed-off-by: Eduardo Otubo <eduardo.otubo@profitbricks.com>
> Signed-off-by: Vadim Galitsyn <vadim.galitsyn@profitbricks.com>
> Reviewed-by: Eugene Crosser <evgenii.cherkashin@profitbricks.com>
> Cc: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Cc: Markus Armbruster <armbru@redhat.com>
> Cc: qemu-devel@nongnu.org
> ---
[...]
> +
> +MemoryInfo *qmp_query_memory(Error **errp)
> +{
> + MemoryInfo *mem_info = g_malloc0(sizeof(MemoryInfo));
> + BalloonInfo *balloon_info;
> + Error *local_err = NULL;
> +
> + mem_info->base_memory = ram_size;
> + mem_info->hot_plug_memory = pc_existing_dimms_capacity(&local_err);
This seems to be x86 specific.
Some machines (e.g. s390x) will not be properly accounted here.
(e.g. they round ram_size up/down) or don't use DIMMs. I think we should
query the machines instead.
> + if (local_err) {
> + error_setg(errp, "could not get hot-plug memory info: %s",
> + error_get_pretty(local_err));
> + g_free(mem_info);
> + return NULL;
> + }
> +
> + /* In case if it is not possible to get balloon info, just ignore it. */
> + balloon_info = qmp_query_balloon(&local_err);
> + if (local_err) {
> + mem_info->ballooned_actual_memory = 0;
> + error_free(local_err);
> + } else {
> + mem_info->ballooned_actual_memory = balloon_info->actual;
> + }
--
Thanks,
David
next prev parent reply other threads:[~2017-06-19 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 12:55 [Qemu-devel] [PATCH] hmp, qmp: introduce "info memory" and "query-memory" commands Vadim Galitsyn
2017-06-13 12:55 ` Vadim Galitsyn
2017-06-13 13:03 ` no-reply
2017-06-13 13:27 ` no-reply
2017-06-19 7:47 ` David Hildenbrand [this message]
2017-06-22 14:06 ` Vadim Galitsyn
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=5c8dbd37-073c-28a8-0062-272c6df02373@redhat.com \
--to=david@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eduardo.otubo@profitbricks.com \
--cc=mohammed.gamal@profitbricks.com \
--cc=qemu-devel@nongnu.org \
--cc=vadim.galitsyn@profitbricks.com \
--cc=vasilis.liaskovitis@profitbricks.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).