From: Luiz Capitulino <lcapitulino@redhat.com>
To: Michal Novotny <minovotn@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] New cpu-max field in query-machines QMP command output
Date: Mon, 8 Apr 2013 10:02:59 -0400 [thread overview]
Message-ID: <20130408100259.5cf4f7f0@redhat.com> (raw)
In-Reply-To: <a7d1f76cb95291dee21569554b4d3ec3718b23de.1365332961.git.minovotn@redhat.com>
On Mon, 8 Apr 2013 12:00:35 +0200
Michal Novotny <minovotn@redhat.com> wrote:
> This alters the query-machines QMP command to output information
> about maximum number of CPUs for each machine type with default
> value 1 in case the number of max_cpus is not set.
>
> Signed-off-by: Michal Novotny <minovotn@redhat.com>
> ---
> qapi-schema.json | 2 +-
> vl.c | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/qapi-schema.json b/qapi-schema.json
> index db542f6..39cae4b 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -2865,7 +2865,7 @@
> ##
> { 'type': 'MachineInfo',
> 'data': { 'name': 'str', '*alias': 'str',
> - '*is-default': 'bool' } }
> + '*is-default': 'bool', 'cpu-max': 'int' } }
Please, document the new field.
Also, how is this affected by the CPU hotplug support?
>
> ##
> # @query-machines:
> diff --git a/vl.c b/vl.c
> index a8bba04..c05b3d3 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -1617,6 +1617,7 @@ MachineInfoList *qmp_query_machines(Error **errp)
> }
>
> info->name = g_strdup(m->name);
> + info->cpu_max = !m->max_cpus ? 1 : m->max_cpus;
>
> entry = g_malloc0(sizeof(*entry));
> entry->value = info;
next prev parent reply other threads:[~2013-04-08 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 10:00 [Qemu-devel] [PATCH] New cpu-max field in query-machines QMP command output Michal Novotny
2013-04-08 14:02 ` Luiz Capitulino [this message]
2013-04-08 14:13 ` Michal Novotny
2013-04-08 16:18 ` Igor Mammedov
2013-04-08 16:21 ` Michal Novotny
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=20130408100259.5cf4f7f0@redhat.com \
--to=lcapitulino@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=minovotn@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.