qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Michal Novotny <minovotn@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] New cpu-max field in query-machines QMP command output
Date: Tue, 9 Apr 2013 09:15:51 -0400	[thread overview]
Message-ID: <20130409091551.6937c656@redhat.com> (raw)
In-Reply-To: <51641301.5000302@redhat.com>

On Tue, 09 Apr 2013 15:09:21 +0200
Michal Novotny <minovotn@redhat.com> wrote:

> 
> On 04/09/2013 03:06 PM, Luiz Capitulino wrote:
> > On Mon, 08 Apr 2013 11:14:32 -0600
> > Eric Blake <eblake@redhat.com> wrote:
> >
> >> On 04/08/2013 10:41 AM, Michal Novotny wrote:
> >>> Alter the query-machines QMP command to output information about
> >>> maximum number of CPUs for each machine type with default value
> >>> set to 1 in case the number of max_cpus is not set.
> >>>
> >>> Signed-off-by: Michal Novotny <minovotn@redhat.com>
> >>> ---
> >>>  qapi-schema.json | 4 +++-
> >>>  vl.c             | 1 +
> >>>  2 files changed, 4 insertions(+), 1 deletion(-)
> >>>
> >>> diff --git a/qapi-schema.json b/qapi-schema.json
> >>> index db542f6..689ca8d 100644
> >>> --- a/qapi-schema.json
> >>> +++ b/qapi-schema.json
> >>> @@ -2861,11 +2861,13 @@
> >>>  #
> >>>  # @default: #optional whether the machine is default
> >>>  #
> >>> +# @cpu-max: maximum number of CPUs supported by the machine type
> >> Typically, when adding a field in a later version than the original
> >> introduction of the datatype, we add '(since 1.5)' to make it obvious
> >> when to expect the field.  However, as nothing (currently) enforces this
> >> rule, I think such an addition is minor enough that it wouldn't
> >> invalidate the use of my:
> > Oh, it turns out I was making some confusion with this patch and
> > didn't realize it was extending the query-machines command.
> >
> > I don't mean there's anything wrong with it, but my question is: doesn't
> > this patch invalidates query-cpu-max?
> 
> Not really, the query-cpu-max shows maximum number of CPUs supported per
> currently running machine (machine type) however the extension to
> query-machines shows the maximum number of CPUs supported per each of
> the displayed machine types. This usually doesn't matter on x86
> architectures however it does matter on ARM, for example, as ARM has
> some CPU models supporting up to 4 CPUs (highbank model) whereas most of
> the ARM processors does have only one CPU.

Can't we eliminate the query-cpu-max command if we extend the
query-machines command to show which machine type is in use?

  reply	other threads:[~2013-04-09 13:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 16:41 [Qemu-devel] [PATCH v2] New cpu-max field in query-machines QMP command output Michal Novotny
2013-04-08 16:35 ` [Qemu-devel] Fwd: " Michal Novotny
2013-04-08 17:14 ` [Qemu-devel] " Eric Blake
2013-04-09 13:06   ` Luiz Capitulino
2013-04-09 13:09     ` Michal Novotny
2013-04-09 13:15       ` Luiz Capitulino [this message]
2013-04-09 13:32         ` Michal Novotny
2013-04-09 13:42           ` Luiz Capitulino
2013-04-09 13:59             ` Michal Novotny
2013-04-09 13:15     ` Peter Krempa

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=20130409091551.6937c656@redhat.com \
    --to=lcapitulino@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 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).