From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34389) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwGi3-0003SL-Pk for qemu-devel@nongnu.org; Mon, 08 Jul 2013 15:02:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UwGi1-0002f3-Hk for qemu-devel@nongnu.org; Mon, 08 Jul 2013 15:02:51 -0400 Received: from mx1.redhat.com ([209.132.183.28]:2757) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwGi1-0002eb-9y for qemu-devel@nongnu.org; Mon, 08 Jul 2013 15:02:49 -0400 Message-ID: <51DB0CD1.7030501@redhat.com> Date: Mon, 08 Jul 2013 13:02:41 -0600 From: Eric Blake MIME-Version: 1.0 References: <1372931597-28115-1-git-send-email-gaowanlong@cn.fujitsu.com> <1372931597-28115-2-git-send-email-gaowanlong@cn.fujitsu.com> <20130705184115.GP13956@otherpad.lan.raisama.net> In-Reply-To: <20130705184115.GP13956@otherpad.lan.raisama.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="----enig2IKIKPCIGXMVGEOTBLPTA" Subject: Re: [Qemu-devel] [PATCH V4 01/10] NUMA: Support multiple CPU ranges on -numa option List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, lcapitulino@redhat.com, bsd@redhat.com, y-goto@jp.fujitsu.com, pbonzini@redhat.com, afaerber@suse.de, Wanlong Gao This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2IKIKPCIGXMVGEOTBLPTA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 07/05/2013 12:41 PM, Eduardo Habkost wrote: > On Thu, Jul 04, 2013 at 05:53:08PM +0800, Wanlong Gao wrote: >> From: Bandan Das >> >> This allows us to use the "cpus" property multiple times >> to specify multiple cpu (ranges) to the -numa option : >> >> -numa node,cpus=3D1,cpus=3D2,cpus=3D4 >> or >> -numa node,cpus=3D1-3,cpus=3D5 >> >> Note that after this patch, the defalut suffix of "-numa node,mem=3DN"= >> will no longer be "M". So we must add the suffix "M" like "-numa node,= mem=3DNM" >> when assigning "N MB" of node memory size. >=20 > Such an incompatible change is not acceptable, as it would break > existing configurations. libvirt doesn't specify any suffix and expects= > it to always mean "MB". Newer libvirt can be taught to append 'M' when it detects it is talking to newer qemu. While you have a point that it is annoying to force users to upgrade to a newer libvirt merely because they upgraded qemu, the libvirt point of view is that the following are supported: old libvirt -> old qemu new libvirt -> old qemu new libvirt -> new qemu but that this combination is always best effort and not required to work:= old libvirt -> new qemu --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org ------enig2IKIKPCIGXMVGEOTBLPTA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJR2wzRAAoJEKeha0olJ0NqKJMH/3k7+c7rUHNDzywzckmXswPF 6xxE7knM36KPz1jyRVRh+4CT8fcr1aek3fPVKUKBDzsDE4Y9kXRcfO7ayqYpRXK+ Qo2+WEOj7Y6BQOO6OJwwXjpdPkJLB/Cxs3G7GVuPK0kUttdVsLVyRKwQOLfvbYZp 4rn3jFsUjv/4m4Rru+BjFZ20X4Hgb9h+mzGTl9I8bOuDx22HtnjjfIb1ImAGlThH XGNxngBpt3Cu99QFgpTUUCxPqgf7sUXhM6FAm8N+MjV/t2xxa7eClgqiBJLIr3EI FYTSN05NlF80xcW4WBpUtheuOqGRKvXuQQFwP/XNELvmENE4hZkVNj9PxMvjzSI= =Jm3b -----END PGP SIGNATURE----- ------enig2IKIKPCIGXMVGEOTBLPTA--