From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Hu Tao" <hutao@cn.fujitsu.com>,
qemu-devel@nongnu.org, "Igor Mammedov" <imammedo@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Wanlong Gao" <gaowanlong@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] Document MAX_CPUMASK_BITS and use it when limiting max_cpus
Date: Wed, 19 Mar 2014 13:21:10 +0200 [thread overview]
Message-ID: <20140319112110.GA27930@redhat.com> (raw)
In-Reply-To: <1395170964-32589-1-git-send-email-ehabkost@redhat.com>
On Tue, Mar 18, 2014 at 04:29:22PM -0300, 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.
Applied, thanks!
> 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(-)
>
> --
> 1.8.5.3
prev parent reply other threads:[~2014-03-19 11:21 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 ` [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 [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=20140319112110.GA27930@redhat.com \
--to=mst@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=lersek@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).