From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Hu Tao <hutao@cn.fujitsu.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 2/4] numa: Reject CPU indexes > max_cpus
Date: Tue, 24 Feb 2015 07:49:36 +0100 [thread overview]
Message-ID: <20150224074936.3be3b13f@nial.brq.redhat.com> (raw)
In-Reply-To: <1423763435-3696-3-git-send-email-ehabkost@redhat.com>
On Thu, 12 Feb 2015 15:50:33 -0200
Eduardo Habkost <ehabkost@redhat.com> wrote:
> CPU index is always less than max_cpus, as documented at sysemu.h:
>
> > The following shall be true for all CPUs:
> > cpu->cpu_index < max_cpus <= MAX_CPUMASK_BITS
>
> Reject configuration which uses invalid CPU indexes.
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Excluding nitpicking below
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> v1 -> v2: (no changes)
>
> v2 -> v3:
> * Check for (cpu >= max_cpus) instead of (cpu > max_cpus)
> * Reword error message as we are not checking for "bigger than maxcpus"
> CPU indexes
> ---
> numa.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/numa.c b/numa.c
> index 41e496b..4139e46 100644
> --- a/numa.c
> +++ b/numa.c
> @@ -76,9 +76,11 @@ static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp)
> }
>
> for (cpus = node->cpus; cpus; cpus = cpus->next) {
> - if (cpus->value >= MAX_CPUMASK_BITS) {
> - error_setg(errp, "CPU number %" PRIu16 " is bigger than %d",
> - cpus->value, MAX_CPUMASK_BITS - 1);
> + if (cpus->value >= max_cpus) {
> + error_setg(errp,
> + "CPU index (%" PRIu16 ")" \
'\' is not really necessary here
> + " should be smaller than maxcpus (%d)",
> + cpus->value, max_cpus);
> return;
> }
> bitmap_set(numa_info[nodenr].node_cpu, cpus->value, 1);
next prev parent reply other threads:[~2015-02-24 6:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 17:50 [Qemu-devel] [PATCH v3 0/4] NUMA: Validate CPU configuration Eduardo Habkost
2015-02-12 17:50 ` [Qemu-devel] [PATCH v3 1/4] numa: Fix off-by-one error at MAX_CPUMASK_BITS check Eduardo Habkost
2015-02-24 6:38 ` Igor Mammedov
2015-02-12 17:50 ` [Qemu-devel] [PATCH v3 2/4] numa: Reject CPU indexes > max_cpus Eduardo Habkost
2015-02-24 6:49 ` Igor Mammedov [this message]
2015-02-12 17:50 ` [Qemu-devel] [PATCH v3 3/4] numa: Reject configuration if CPU appears on multiple nodes Eduardo Habkost
2015-02-24 7:04 ` Igor Mammedov
2015-02-12 17:50 ` [Qemu-devel] [PATCH v3 4/4] numa: Print warning if no node is assigned to a CPU Eduardo Habkost
2015-02-12 18:22 ` Paolo Bonzini
2015-02-12 23:05 ` Eduardo Habkost
2015-02-24 8:01 ` Igor Mammedov
2015-02-24 18:19 ` Eduardo Habkost
2015-02-25 8:43 ` Igor Mammedov
2015-02-23 20:10 ` [Qemu-devel] [PATCH v3 0/4] NUMA: Validate CPU configuration Eduardo Habkost
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=20150224074936.3be3b13f@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=ehabkost@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).