From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:48755) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ShpYL-0005HM-Q0 for qemu-devel@nongnu.org; Thu, 21 Jun 2012 18:08:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ShpYK-0002cA-4i for qemu-devel@nongnu.org; Thu, 21 Jun 2012 18:08:37 -0400 Received: from va3ehsobe002.messaging.microsoft.com ([216.32.180.12]:25063 helo=va3outboundpool.messaging.microsoft.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ShpYK-0002bu-0s for qemu-devel@nongnu.org; Thu, 21 Jun 2012 18:08:36 -0400 Message-ID: <4FE394A2.8070709@amd.com> Date: Thu, 21 Jun 2012 23:39:46 +0200 From: Andre Przywara MIME-Version: 1.0 References: <20120621175125.GJ5073@otherpad.lan.raisama.net> In-Reply-To: <20120621175125.GJ5073@otherpad.lan.raisama.net> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] qemu -numa option and non-contiguous CPU ranges List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: libvir-list@redhat.com, qemu-devel@nongnu.org, Bharata B Rao On 06/21/2012 07:51 PM, Eduardo Habkost wrote: > Hi, > > I just noticed libvirt tries to use the -numa option in a way that qemu > never understood: if a node is configured to have a non-contiguous set > of CPUs, it tries to generate a command-line option that looks like: > > "-numa node,nodeid=...,cpus=0,2,4,mem=..." > ^^^^^ > > But this format was never supported by qemu. This format is even a bit > weird, as "," is an option separator, and it is being used as a > separator _inside_ an option. Exactly this was the reason back then to not support non-contiguous set of CPUs. Inside qemu there is no reason why this shouldn't work, it was just hard to write on the command line. So after a short discussion we decided to drop this for the time being. If you have a great idea how to specify this (I think a comma will not work, because it will be catched earlier), I am all ears. Regards, Andre. > My question is: should we support this option format in qemu, or should > we change libvirt to use another format (that has yet to be implemented, > because currently there's no way to specify a non-contiguous set of CPUs > for a NUMA node). > > Any suggestions? > -- Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany