From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Hu Tao" <hutao@cn.fujitsu.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Wanlong Gao" <gaowanlong@cn.fujitsu.com>
Subject: [Qemu-devel] [PATCH 1/2] sysemu.h: Document what MAX_CPUMASK_BITS really limits
Date: Tue, 18 Mar 2014 16:29:23 -0300 [thread overview]
Message-ID: <1395170964-32589-2-git-send-email-ehabkost@redhat.com> (raw)
In-Reply-To: <1395170964-32589-1-git-send-email-ehabkost@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
include/sysemu/sysemu.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/sysemu/sysemu.h b/include/sysemu/sysemu.h
index c01304d..865e5f0 100644
--- a/include/sysemu/sysemu.h
+++ b/include/sysemu/sysemu.h
@@ -133,7 +133,14 @@ extern uint8_t qemu_extra_params_fw[2];
extern QEMUClockType rtc_clock;
#define MAX_NODES 64
+
+/* The following shall be true for all CPUs:
+ * cpu->cpu_index < max_cpus <= MAX_CPUMASK_BITS
+ *
+ * Note that cpu->get_arch_id() may be larger than MAX_CPUMASK_BITS.
+ */
#define MAX_CPUMASK_BITS 255
+
extern int nb_numa_nodes;
extern uint64_t node_mem[MAX_NODES];
extern unsigned long *node_cpumask[MAX_NODES];
--
1.8.5.3
next prev parent reply other threads:[~2014-03-18 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 19:29 [Qemu-devel] [PATCH 0/2] Document MAX_CPUMASK_BITS and use it when limiting max_cpus Eduardo Habkost
2014-03-18 19:29 ` Eduardo Habkost [this message]
2014-03-18 19:29 ` [Qemu-devel] [PATCH 2/2] vl.c: Use MAX_CPUMASK_BITS macro instead of hardcoded constant Eduardo Habkost
2014-03-18 19:40 ` [Qemu-devel] [PATCH 0/2] Document MAX_CPUMASK_BITS and use it when limiting max_cpus Laszlo Ersek
2014-03-19 11:21 ` Michael S. Tsirkin
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=1395170964-32589-2-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=gaowanlong@cn.fujitsu.com \
--cc=hutao@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@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).