From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38990)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mjt@tls.msk.ru>) id 1Upd8R-0005gx-8v
	for qemu-devel@nongnu.org; Thu, 20 Jun 2013 07:34:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mjt@tls.msk.ru>) id 1Upd8O-0000PA-MX
	for qemu-devel@nongnu.org; Thu, 20 Jun 2013 07:34:39 -0400
Received: from isrv.corpit.ru ([86.62.121.231]:33113)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mjt@tls.msk.ru>) id 1Upd8O-0000Ou-Fh
	for qemu-devel@nongnu.org; Thu, 20 Jun 2013 07:34:36 -0400
Message-ID: <51C2E8C9.9030503@msgid.tls.msk.ru>
Date: Thu, 20 Jun 2013 15:34:33 +0400
From: Michael Tokarev <mjt@tls.msk.ru>
MIME-Version: 1.0
References: <jpgd2rjfaeq.fsf@redhat.com>
	<20130619134252.22bdbc37@nial.usersys.redhat.com>
	<20130619132642.GD2825@otherpad.lan.raisama.net>
	<20130620113030.79943476@nial.usersys.redhat.com>
	<51C2D0EA.7060204@redhat.com>
In-Reply-To: <51C2D0EA.7060204@redhat.com>
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: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
Cc: Anthony Liguori <aliguori@us.ibm.com>, Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>, Bandan Das <bsd@redhat.com>, Igor Mammedov <imammedo@redhat.com>

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?

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),
but it is rather non-standard.

Thanks,

/mjt