From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51057)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vasilis.liaskovitis@profitbricks.com>)
	id 1UymRh-0003fu-Eh
	for qemu-devel@nongnu.org; Mon, 15 Jul 2013 13:20:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vasilis.liaskovitis@profitbricks.com>)
	id 1UymRe-0008EM-7U
	for qemu-devel@nongnu.org; Mon, 15 Jul 2013 13:20:21 -0400
Received: from mail-ea0-f172.google.com ([209.85.215.172]:49360)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vasilis.liaskovitis@profitbricks.com>)
	id 1UymRe-0008C6-1J
	for qemu-devel@nongnu.org; Mon, 15 Jul 2013 13:20:18 -0400
Received: by mail-ea0-f172.google.com with SMTP id q10so7975843eaj.31
	for <qemu-devel@nongnu.org>; Mon, 15 Jul 2013 10:20:17 -0700 (PDT)
Date: Mon, 15 Jul 2013 19:20:13 +0200
From: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>
Message-ID: <20130715172013.GD11958@dhcp-192-168-178-175.profitbricks.localdomain>
References: <cover.1372234719.git.hutao@cn.fujitsu.com>
	<6b5ff346b23fba9a8707507fda7f9b71719a55be.1372234719.git.hutao@cn.fujitsu.com>
	<51CAB866.2080507@redhat.com> <51CBC8B3.8070708@cn.fujitsu.com>
	<51CBE1DD.9020301@redhat.com>
	<20130715170551.GC11958@dhcp-192-168-178-175.profitbricks.localdomain>
	<51E42D06.9080004@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51E42D06.9080004@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 05/14] vl: handle "-device dimm"
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>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Hu Tao <hutao@cn.fujitsu.com>, Bandan Das <bsd@redhat.com>, Eduardo Habkost <ehabkost@redhat.com>, gaowanlong@cn.fujitsu.com, qemu-devel@nongnu.org

On Mon, Jul 15, 2013 at 07:10:30PM +0200, Paolo Bonzini wrote:
> Il 15/07/2013 19:05, Vasilis Liaskovitis ha scritto:
> > from what i understand, we are currently favoring this numa option? (I saw it
> > mentioned in Gao's numa patchset series as well)
> 
> The two patchsets have some overlap, so it's good to find a design that
> fits both.
> 
> > There is still the question of "how many hotpluggable dimm devices does this
> > memory range describe?". With the dimm device that was clearly defined, but not
> > so with this option. Do we choose a default granularity e.g. 1 GB?
> 
> I think it's the same.  One "-numa mem" option = one "-device dimm"
> option; both define one range.  Unused memory ranges may remain if you

ah ok, I get the proposal now.

> stumble upon a unusable range such as the PCI window.  For example two
> "-numa mem,size=2G" options would allocate memory from 0 to 2G and from
> 4 to 6G.

ok, that's done already.

thanks,

- Vasilis