From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Hu Tao <hutao@cn.fujitsu.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/3] NUMA: Validate CPU configuration
Date: Mon, 9 Feb 2015 17:53:13 -0200 [thread overview]
Message-ID: <1423511596-2584-1-git-send-email-ehabkost@redhat.com> (raw)
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
Eduardo Habkost (3):
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 | 45 ++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 42 insertions(+), 3 deletions(-)
--
2.1.0
next reply other threads:[~2015-02-09 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 19:53 Eduardo Habkost [this message]
2015-02-09 19:53 ` [Qemu-devel] [PATCH v2 1/3] numa: Reject CPU indexes > max_cpus Eduardo Habkost
2015-02-12 13:42 ` Igor Mammedov
2015-02-09 19:53 ` [Qemu-devel] [PATCH v2 2/3] numa: Reject configuration if CPU appears on multiple nodes Eduardo Habkost
2015-02-12 14:22 ` Igor Mammedov
2015-02-12 15:18 ` Paolo Bonzini
2015-02-12 15:26 ` Eduardo Habkost
2015-02-12 16:04 ` Igor Mammedov
2015-02-12 15:01 ` Igor Mammedov
2015-02-12 15:24 ` Eduardo Habkost
2015-02-12 16:01 ` Igor Mammedov
2015-02-12 17:54 ` Eduardo Habkost
2015-02-09 19:53 ` [Qemu-devel] [PATCH v2 3/3] numa: Print warning if no node is assigned to a CPU 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=1423511596-2584-1-git-send-email-ehabkost@redhat.com \
--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 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).