From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47989) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYyQh-0003Pa-E8 for qemu-devel@nongnu.org; Fri, 20 Mar 2015 11:01:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YYyQc-0004Jo-2I for qemu-devel@nongnu.org; Fri, 20 Mar 2015 11:01:43 -0400 Date: Fri, 20 Mar 2015 16:01:34 +0100 From: Igor Mammedov Message-ID: <20150320160134.7423f24f@nial.brq.redhat.com> In-Reply-To: <20150320145246.GT3513@thinpad.lan.raisama.net> References: <1426784962-7541-1-git-send-email-imammedo@redhat.com> <20150320112414.0efb6f94@nial.brq.redhat.com> <20150320145246.GT3513@thinpad.lan.raisama.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 for-2.3 0/2] numa: Fix default VCPUs to node mapping List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org On Fri, 20 Mar 2015 11:52:46 -0300 Eduardo Habkost wrote: > On Fri, Mar 20, 2015 at 11:24:14AM +0100, Igor Mammedov wrote: > > On Thu, 19 Mar 2015 17:09:20 +0000 > > Igor Mammedov wrote: > > > > > Changes since v2: > > > - fix spelling errors > > > - split out PC hunks itno a separate patch > > > > > > Igor Mammedov (2): > > > numa: introduce machine callback for VCPU to node mapping > > > pc: fix default VCPU to NUMA node mapping > > > > > > hw/i386/pc.c | 9 +++++++++ > > > include/hw/boards.h | 5 +++++ > > > include/sysemu/numa.h | 3 ++- > > > numa.c | 18 +++++++++++++----- > > > vl.c | 2 +- > > > 5 files changed, 30 insertions(+), 7 deletions(-) > > > > > > > CCing stable which I've forgotten to do earlier > > Why stable? This can be easily worked around by explicitly setting the > CPUs for each node. I see this as an usbility improvement, not a bug > fix. And it breaks compatibility. For me if guest hangs due to incorrect topology provided by QEMU, it's a bug. I'm not sure about what compatibility it breaks though, but I won't insist on making downstream (2.2 based) live easier in this case since there is workaround.