qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michal Novotny <minovotn@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] New QMP command query-cpu-max and HMP command cpu_max
Date: Mon, 25 Mar 2013 17:24:02 +0100	[thread overview]
Message-ID: <51507A22.2050101@redhat.com> (raw)
In-Reply-To: <20130325121327.0aef9200@redhat.com>


On 03/25/2013 05:13 PM, Luiz Capitulino wrote:
> On Mon, 25 Mar 2013 16:58:50 +0100
> Michal Novotny <minovotn@redhat.com> wrote:
>
>> These commands return the maximum number of CPUs supported by the
> /These commands/This command


I meant both of them - both QMP (query-cpu-max) one HMP (cpu_max) one.


>
>> currently running emulator instance, as defined in its QEMUMachine
>> struct.
>>
>> Signed-off-by: Michal Novotny <minovotn@redhat.com>
>> ---
>>  hmp-commands.hx  | 14 ++++++++++++++
>>  hmp.c            | 15 +++++++++++++++
>>  hmp.h            |  1 +
>>  qapi-schema.json | 11 +++++++++++
>>  qmp-commands.hx  | 22 ++++++++++++++++++++++
>>  vl.c             |  5 +++++
>>  6 files changed, 68 insertions(+)
>>
>> diff --git a/hmp-commands.hx b/hmp-commands.hx
>> index df44906..c976459 100644
>> --- a/hmp-commands.hx
>> +++ b/hmp-commands.hx
>> @@ -690,6 +690,20 @@ Set the default CPU.
>>  ETEXI
>>  
>>      {
>> +        .name       = "cpu_max",
>> +        .args_type  = "",
>> +        .params     = "",
>> +        .help       = "Get maximum number of VCPUs supported by machine",
>> +        .mhandler.cmd = hmp_query_cpu_max,
>> +    },
>> +
>> +STEXI
>> +@item cpu_max
>> +@findex cpu_max
>> +Returns the number of CPUs supported by the machine being emulated.
>> +ETEXI
>> +
>> +    {
>>          .name       = "mouse_move",
>>          .args_type  = "dx_str:s,dy_str:s,dz_str:s?",
>>          .params     = "dx dy [dz]",
>> diff --git a/hmp.c b/hmp.c
>> index b0a861c..6d5674f 100644
>> --- a/hmp.c
>> +++ b/hmp.c
>> @@ -748,6 +748,21 @@ void hmp_ringbuf_read(Monitor *mon, const QDict *qdict)
>>      g_free(data);
>>  }
>>  
>> +void hmp_query_cpu_max(Monitor *mon, const QDict *qdict)
>> +{
>> +    int cpu_max;
>> +    Error *errp = NULL;
>> +
>> +    cpu_max = qmp_query_cpu_max(&errp);
>> +    if (errp) {
>> +        monitor_printf(mon, "%s\n", error_get_pretty(errp));
>> +        error_free(errp);
>> +        return;
>> +    }
> Sorry for not noticing this before, but you can pass NULL to
> qmp_query_cpu_max(), as it never fails.


Ok, I just went according to the docs and there was no mention about
it's possible to pass NULL. I don't know what magic qemu does with that
one so I rather don't pass NULL. However, respin necessary?

Michal

-- 
Michal Novotny <minovotn@redhat.com>, RHCE, Red Hat
Virtualization | libvirt-php bindings | php-virt-control.org

  reply	other threads:[~2013-03-25 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 15:58 [Qemu-devel] [PATCH v2] New QMP command query-cpu-max and HMP command cpu_max Michal Novotny
2013-03-25 16:13 ` Luiz Capitulino
2013-03-25 16:24   ` Michal Novotny [this message]
2013-03-25 16:27     ` Luiz Capitulino
2013-03-25 16:31       ` 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=51507A22.2050101@redhat.com \
    --to=minovotn@redhat.com \
    --cc=lcapitulino@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 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).