From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch 2/2] machine struct - specify max_cpus at the per machine level
Date: Thu, 9 Oct 2008 04:05:51 +0200 [thread overview]
Message-ID: <fb249edb0810081905j3edcdc1bq2f5a3021cfcaabc4@mail.gmail.com> (raw)
In-Reply-To: <yq04p3ngq7g.fsf@jaguar.mkp.net>
2008/10/8 Jes Sorensen <jes@sgi.com>:
> andrzej> No machine has 0 cpus so there's no point specifying = 1 in
> andrzej> every machine instead of making it the default. The other
> andrzej> fields were thought so that they don't have to be specified
> andrzej> except for non-default values.
>
> Well making 0 mean 1 is even worse, and adding a 1 in those isn't
Why? 0 can only mean that the field was left out.
Regards
prev parent reply other threads:[~2008-10-09 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 13:11 [Qemu-devel] [patch 2/2] machine struct - specify max_cpus at the per machine level Jes Sorensen
2008-10-07 20:40 ` Anthony Liguori
2008-10-07 21:30 ` andrzej zaborowski
2008-10-08 13:40 ` Jes Sorensen
2008-10-09 2:05 ` andrzej zaborowski [this message]
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=fb249edb0810081905j3edcdc1bq2f5a3021cfcaabc4@mail.gmail.com \
--to=balrogg@gmail.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).