From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: "Andreas Färber" <afaerber@suse.de>,
"Eduardo Habkost" <ehabkost@redhat.com>,
kvm@vger.kernel.org, gleb@redhat.com, libvir-list@redhat.com,
mtosatti@redhat.com,
"qemu-devel developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] kvm: warn if num cpus is greater than num recommended
Date: Mon, 26 Aug 2013 09:43:35 +0200 [thread overview]
Message-ID: <521B0727.30602@redhat.com> (raw)
In-Reply-To: <795650865.3095841.1377257598867.JavaMail.root@redhat.com>
Il 23/08/2013 13:33, Andrew Jones ha scritto:
> Does smp_cpus map to the current
> number of cpus, or to the number of possible cpus? If it maps to the number
> of possible cpus, then this is the right place. If the former, then I guess
> it'll take more thought. I'ved added Igor (still on vacation) to this reply,
> but regardless I vote we worry about hot-plug limit checking in different
> patch.
smp_cpus is the initial number, max_cpus is the number of possible cpus.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, gleb@redhat.com, libvir-list@redhat.com,
mtosatti@redhat.com,
"qemu-devel developers" <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] kvm: warn if num cpus is greater than num recommended
Date: Mon, 26 Aug 2013 09:43:35 +0200 [thread overview]
Message-ID: <521B0727.30602@redhat.com> (raw)
In-Reply-To: <795650865.3095841.1377257598867.JavaMail.root@redhat.com>
Il 23/08/2013 13:33, Andrew Jones ha scritto:
> Does smp_cpus map to the current
> number of cpus, or to the number of possible cpus? If it maps to the number
> of possible cpus, then this is the right place. If the former, then I guess
> it'll take more thought. I'ved added Igor (still on vacation) to this reply,
> but regardless I vote we worry about hot-plug limit checking in different
> patch.
smp_cpus is the initial number, max_cpus is the number of possible cpus.
Paolo
next prev parent reply other threads:[~2013-08-26 7:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 15:39 [PATCH] kvm: warn if num cpus is greater than num recommended Andrew Jones
2013-08-22 15:39 ` [Qemu-devel] " Andrew Jones
2013-08-22 16:12 ` Eduardo Habkost
2013-08-22 16:12 ` [Qemu-devel] " Eduardo Habkost
2013-08-22 16:21 ` Andreas Färber
2013-08-23 11:33 ` Andrew Jones
2013-08-23 11:33 ` Andrew Jones
2013-08-26 7:43 ` Paolo Bonzini [this message]
2013-08-26 7:43 ` Paolo Bonzini
2013-08-26 8:00 ` Andrew Jones
2013-08-26 8:00 ` Andrew Jones
2013-08-22 16:38 ` Paolo Bonzini
2013-08-22 16:38 ` [Qemu-devel] " Paolo Bonzini
2013-08-23 11:35 ` Andrew Jones
2013-08-23 11:35 ` Andrew Jones
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=521B0727.30602@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=mtosatti@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.