From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Hu Tao <hutao@cn.fujitsu.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/4] NUMA: Validate CPU configuration
Date: Mon, 23 Feb 2015 17:10:28 -0300 [thread overview]
Message-ID: <20150223201028.GD31950@thinpad.lan.raisama.net> (raw)
In-Reply-To: <1423763435-3696-1-git-send-email-ehabkost@redhat.com>
Ping? Can somebody help review this?
On Thu, Feb 12, 2015 at 03:50:31PM -0200, Eduardo Habkost wrote:
> This adds extra checks to the NUMA code to make sure the CPU configuration is
> consistent. This needs to be applied on top of the following series:
>
> Message-Id: <1423421482-11619-1-git-send-email-ehabkost@redhat.com>
> Subject: [Qemu-devel] [PATCH 0/7] NUMA code cleanup
> From: Eduardo Habkost <ehabkost@redhat.com>
> Date: Sun, 8 Feb 2015 16:51:15 -0200
> Git tree: https://github.com/ehabkost/qemu.git numa-next
>
> Changes v1 -> v2:
> * (none, v1 was tagged by accident and never sent to qemu-devel)
>
> Changes v2 -> v3:
> * Fix off-by-one error on CPU index check
> * Use GString and error_report() instead of calling fprintf() directly
> * Simplify logic of the CPUs-not-present check
>
> Eduardo Habkost (4):
> numa: Fix off-by-one error at MAX_CPUMASK_BITS check
> numa: Reject CPU indexes > max_cpus
> numa: Reject configuration if CPU appears on multiple nodes
> numa: Print warning if no node is assigned to a CPU
>
> numa.c | 53 ++++++++++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 50 insertions(+), 3 deletions(-)
>
> --
> 2.1.0
>
>
--
Eduardo
prev parent reply other threads:[~2015-02-23 20:11 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
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 ` Eduardo Habkost [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=20150223201028.GD31950@thinpad.lan.raisama.net \
--to=ehabkost@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=imammedo@redhat.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 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.