From: Laszlo Ersek <lersek@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: "Igor Mammedov" <imammedo@redhat.com>,
"Hu Tao" <hutao@cn.fujitsu.com>,
"Andreas Färber" <afaerber@suse.de>,
"Wanlong Gao" <gaowanlong@cn.fujitsu.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] Document MAX_CPUMASK_BITS and use it when limiting max_cpus
Date: Tue, 18 Mar 2014 20:40:37 +0100 [thread overview]
Message-ID: <5328A135.4010803@redhat.com> (raw)
In-Reply-To: <1395170964-32589-1-git-send-email-ehabkost@redhat.com>
On 03/18/14 20:29, Eduardo Habkost wrote:
> Small rework of patches 6/7 and 7/7 from the previous APIC-ID-limit series I
> sent (which broke the build and where reverted).
>
> Instead of renaming MAX_CPUMASK_BITS like I did previously, just document it
> and use it on the (max_cpus > 255) check on vl.c.
>
> Eduardo Habkost (2):
> sysemu.h: Document what MAX_CPUMASK_BITS really limits
> vl.c: Use MAX_CPUMASK_BITS macro instead of hardcoded constant
>
> include/sysemu/sysemu.h | 7 +++++++
> vl.c | 2 +-
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
series
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
next prev parent reply other threads:[~2014-03-18 19:41 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 ` [Qemu-devel] [PATCH 1/2] sysemu.h: Document what MAX_CPUMASK_BITS really limits Eduardo Habkost
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 ` Laszlo Ersek [this message]
2014-03-19 11:21 ` [Qemu-devel] [PATCH 0/2] Document MAX_CPUMASK_BITS and use it when limiting max_cpus 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=5328A135.4010803@redhat.com \
--to=lersek@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=gaowanlong@cn.fujitsu.com \
--cc=hutao@cn.fujitsu.com \
--cc=imammedo@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 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.