From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, qemu-ppc@nongnu.org,
Eduardo Habkost <ehabkost@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
Andrew Jones <drjones@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/5] numa: code consolidation and fixes
Date: Tue, 23 May 2017 16:38:45 +0200 [thread overview]
Message-ID: <1495550330-34087-1-git-send-email-imammedo@redhat.com> (raw)
changelog since v1:
(Eduardo)
- user error_abort in numa_cpu_pre_plug()
- make default_mapping boolean
- redo default mapping detection loop as a combo of for/if
- return back lost TODO comment
- new patch removing numa_node from generic CPUState
- drop silence test patch as it's already in pull req on list
- new patch [3/5] to fix missing _PXM/fdt nodes for implicitly mapped CPUs
- new patch dropping fallback to node 0
git repo for testing:
https://github.com/imammedo/qemu.git cphp_numa_cfg_follow_up_v3_cleanups_v2
CC: qemu-arm@nongnu.org
CC: qemu-ppc@nongnu.org
CC: Eduardo Habkost <ehabkost@redhat.com>
CC: David Gibson <david@gibson.dropbear.id.au>
CC: Andrew Jones <drjones@redhat.com>
Igor Mammedov (5):
numa: consolidate cpu_preplug fixups/checks for pc/arm/spapr
numa: move default mapping init to machine
numa: make sure that all cpus in has has_node_id set if numa is
enabled
numa: fallback to default NUMA node instead of node 0
numa: move numa_node from CPUState into target specific classes
include/qom/cpu.h | 2 --
include/sysemu/numa.h | 1 +
target/arm/cpu.h | 2 ++
target/i386/cpu.h | 1 +
target/ppc/cpu.h | 1 +
hw/arm/virt-acpi-build.c | 4 +---
hw/arm/virt.c | 16 ++--------------
hw/core/machine.c | 34 ++++++++++++++++++++++++----------
hw/i386/acpi-build.c | 3 +--
hw/i386/pc.c | 21 ++-------------------
hw/ppc/spapr.c | 41 ++++++++++++-----------------------------
hw/ppc/spapr_cpu_core.c | 4 +++-
monitor.c | 11 +++++++----
numa.c | 43 +++++++++++++++++--------------------------
target/arm/cpu.c | 2 +-
target/i386/cpu.c | 2 +-
16 files changed, 76 insertions(+), 112 deletions(-)
--
2.7.4
next reply other threads:[~2017-05-23 14:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 14:38 Igor Mammedov [this message]
2017-05-23 14:38 ` [Qemu-devel] [PATCH v2 1/5] numa: consolidate cpu_preplug fixups/checks for pc/arm/spapr Igor Mammedov
2017-05-26 15:01 ` Eduardo Habkost
2017-05-26 15:33 ` Eduardo Habkost
2017-05-23 14:38 ` [Qemu-devel] [PATCH v2 2/5] numa: move default mapping init to machine Igor Mammedov
2017-05-26 15:02 ` Eduardo Habkost
2017-05-23 14:38 ` [Qemu-devel] [PATCH v2 3/5] numa: make sure that all cpus in has has_node_id set if numa is enabled Igor Mammedov
2017-05-26 16:06 ` Eduardo Habkost
2017-05-29 11:45 ` Igor Mammedov
2017-05-29 13:22 ` Eduardo Habkost
2017-05-23 14:38 ` [Qemu-devel] [PATCH v2 4/5] numa: fallback to default NUMA node instead of node 0 Igor Mammedov
2017-05-23 14:48 ` Eduardo Habkost
2017-05-23 15:44 ` Igor Mammedov
2017-05-26 14:58 ` Eduardo Habkost
2017-05-29 9:12 ` Igor Mammedov
2017-05-29 12:11 ` Igor Mammedov
2017-05-23 14:38 ` [Qemu-devel] [PATCH v2 5/5] numa: move numa_node from CPUState into target specific classes Igor Mammedov
2017-05-26 18:25 ` Eduardo Habkost
2017-05-29 12:12 ` Igor Mammedov
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=1495550330-34087-1-git-send-email-imammedo@redhat.com \
--to=imammedo@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).