From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36218) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpeVj-0000VE-BO for qemu-devel@nongnu.org; Thu, 20 Jun 2013 09:02:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UpeVe-0005QJ-M3 for qemu-devel@nongnu.org; Thu, 20 Jun 2013 09:02:47 -0400 Received: from mail-qe0-f54.google.com ([209.85.128.54]:57931) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpeVe-0005QA-JD for qemu-devel@nongnu.org; Thu, 20 Jun 2013 09:02:42 -0400 Received: by mail-qe0-f54.google.com with SMTP id ne12so3966291qeb.13 for ; Thu, 20 Jun 2013 06:02:41 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <51C2FD68.3090102@redhat.com> Date: Thu, 20 Jun 2013 15:02:32 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <20130619134252.22bdbc37@nial.usersys.redhat.com> <20130619132642.GD2825@otherpad.lan.raisama.net> <20130620113030.79943476@nial.usersys.redhat.com> <51C2D0EA.7060204@redhat.com> <51C2E8C9.9030503@msgid.tls.msk.ru> In-Reply-To: <51C2E8C9.9030503@msgid.tls.msk.ru> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3] vl.c: Support multiple CPU ranges on -numa option List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Tokarev Cc: Anthony Liguori , Eduardo Habkost , Markus Armbruster , qemu-devel@nongnu.org, Bandan Das , Igor Mammedov Il 20/06/2013 13:34, Michael Tokarev ha scritto: > 20.06.2013 13:52, Paolo Bonzini wrote: >> Il 20/06/2013 11:30, Igor Mammedov ha scritto: >>>>> libvirt uses the "cpus" option already, so we have to keep it working. >>> Sure, we can leave it as it's now for some time while a new interface is >>> introduced/adopted. And than later deprecate "cpus". >> >> So, you used a new name because the new behavior of "-numa >> node,cpus=1-2,cpus=3-4" would be incompatible with the old. > > BTW, as I tried to touch exactly the same place yesterday (trying > to convert it to QemuOpts) -- what does this "node" mean? > > For example, with > > -device [type=]devicetype,foo=bar,xzy=abc > > this creates a new device for each "invocation" of option. But > what does this `-numa node' mean? Can there be anything else > besides node? Why it is needed/used for? Nothing, I think it's just that somebody took inspiration from "-device". :) > This -numa option is the last one which uses the old option > parsing mechanism (there's also some smbios-related thing > but it's simple to convert, I almost got it ready yesterday), That would be awesome. Paolo