All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Michal Novotny <minovotn@redhat.com>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Introduce query-cpu-max QMP command and cpu_max HMP counterpart
Date: Tue, 19 Mar 2013 13:28:14 +0100	[thread overview]
Message-ID: <87k3p3bmld.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <e3a6017620c95128121a9748d7a81faf526a08f5.1363104087.git.minovotn@redhat.com> (Michal Novotny's message of "Tue, 12 Mar 2013 17:02:16 +0100")

Please cc: Luiz and me on QMP work in the future.

Michal Novotny <minovotn@redhat.com> writes:

> This is the patch to introduce the query-cpu-max QMP command to get
> the maximum number of CPUs supported by the currently running emulator
> instance. This may differ machine from machine as defined by -machine
> settings and max_cpus member of QEMUMachine structure.

Humor me: don't start commit message bodies with "This patch" or
variations thereof, and don't repeat the subject.  Suggest:

QMP command query-cpu-max returns the maximum number of CPUs supported
by the currently running emulator instance, as defined in its
QEMUMachine struct.

> It's been tested both using QMP/qmp utility and telnet session on
> the QEMU session.

What's a QMP/qmp utility?  Let's drop this sentence.  In the future,
feel free to put testing info below the "---" line.

> The HMP counterpart called cpu_max has been introduced by this patch
> too.

Grammar nit: s/has been/is/.  Even better, avoid passive voice.

Hmm, I just rewrote most of your commit message, so why not rewrite all
of it:

    New QMP command query-cpu-max and HMP command cpu_max

    These commands return the maximum number of CPUs supported by the
    currently running emulator instance, as defined in its QEMUMachine
    struct.

Perhaps Luiz can fix up the commit message commit, if you don't mind.

Patch looks good.

Should query commands for machine properties multiply, we should
consider creating a single command returning all of them.  I'm not
asking you to do that now.

Reviewed-by: Markus Armbruster <armbru@redhat.com>

  parent reply	other threads:[~2013-03-19 12:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 16:03 [Qemu-devel] [PATCH] Introduce query-cpu-max QMP command and cpu_max HMP counterpart Michal Novotny
2013-03-13 20:40 ` Eric Blake
2013-03-19 12:28 ` Markus Armbruster [this message]
2013-03-19 13:00   ` Michal Novotny
2013-03-19 13:27   ` Andreas Färber
2013-03-19 13:33     ` Michal Novotny
2013-03-21 12:51 ` Luiz Capitulino
2013-03-25 12:06   ` Michal Novotny
2013-03-25 15:52     ` Luiz Capitulino
2013-03-25 15:59       ` 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=87k3p3bmld.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=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 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.