From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42621)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1VTfSD-0003sx-9c
	for qemu-devel@nongnu.org; Tue, 08 Oct 2013 18:08:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1VTfS7-0004l9-Az
	for qemu-devel@nongnu.org; Tue, 08 Oct 2013 18:08:33 -0400
Received: from mx1.redhat.com ([209.132.183.28]:24655)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1VTfS7-0004kz-2U
	for qemu-devel@nongnu.org; Tue, 08 Oct 2013 18:08:27 -0400
Received: from int-mx12.intmail.prod.int.phx2.redhat.com
	(int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r98M8Q2J012410
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <qemu-devel@nongnu.org>; Tue, 8 Oct 2013 18:08:26 -0400
Date: Tue, 8 Oct 2013 19:03:29 -0300
From: Marcelo Tosatti <mtosatti@redhat.com>
Message-ID: <20131008220329.GB16625@amt.cnet>
References: <20131008004126.773017235@amt.cnet>
	<874n8sp68n.fsf@blackfin.pond.sub.org> <5253BC12.90105@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5253BC12.90105@redhat.com>
Subject: Re: [Qemu-devel] [patch 0/2] force -mem-path RAM allocation
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: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org

On Tue, Oct 08, 2013 at 10:02:26AM +0200, Paolo Bonzini wrote:
> Il 08/10/2013 09:32, Markus Armbruster ha scritto:
> > We have
> > 
> >     -mem-path FILE  provide backing storage for guest RAM
> >     -mem-prealloc   preallocate guest memory (use with -mem-path)
> > 
> > PATCH 2/2 adds
> > 
> >     -mem-path-force    fail if unable to allocate RAM as specified by -mem-path
> > 
> > Looks like it's time to consolidate the options related to guest memory
> > into a single, QemuOpts-style -memory NAME=VALUE,...  What do you guys
> > think?
> 
> Yes, we can use "-numa memory" (or "-numa mem") that Wanlong Gao is
> adding.  We can add path=, preallocate= and force= options there.
> 
> Paolo

It would be important for the new option to be backportable 
independently. Therefore mixing it with -numa is not an option.

Also due to backportability supporting a new style of command line
for -mem-path is problematic (management must be changed accordingly).

Can the new option format for memory be created incrementally on 
top of -mem-path-force? (agree its a good thing, it avoids proliferation
of new options).