From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: file_ram_alloc: unify mem-path,mem-prealloc error handling Date: Tue, 4 Feb 2014 13:43:14 -0500 Message-ID: <20140204184314.GA25613@amt.cnet> References: <20140204184153.GA25368@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Paolo Bonzini To: qemu-devel , kvm-devel Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50598 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752165AbaBDSnb (ORCPT ); Tue, 4 Feb 2014 13:43:31 -0500 Content-Disposition: inline In-Reply-To: <20140204184153.GA25368@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Feb 04, 2014 at 01:41:53PM -0500, Marcelo Tosatti wrote: > > -mem-prealloc asks to preallocate memory residing on -mem-path path. > > Currently QEMU exits in case: > > - Memory file has been created but allocation via explicit write > fails. > > And it fallbacks to malloc in case: > - Querying huge page size fails. > - Lack of sync MMU support. > - Open fails. > - mmap fails. > > Have the same behaviour for all cases: fail in case -mem-path and > -mem-prealloc are specified for regions where the requested size is > suitable for hugepages. > > Signed-off-by: Marcelo Tosatti Forgot uq/master on the subject (but its aimed for that tree).