From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=52936 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Oh22H-0003lL-0j
	for qemu-devel@nongnu.org; Thu, 05 Aug 2010 11:07:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1Oh22E-000403-SM
	for qemu-devel@nongnu.org; Thu, 05 Aug 2010 11:07:08 -0400
Received: from mx1.redhat.com ([209.132.183.28]:59954)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1Oh22E-0003zt-J3
	for qemu-devel@nongnu.org; Thu, 05 Aug 2010 11:07:06 -0400
Message-ID: <4C5A7A2D.5000507@redhat.com>
Date: Thu, 05 Aug 2010 11:45:33 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with
	Linux 2.6.35?
References: <20100804130709.GL10499@redhat.com>
	<4C5967D8.7080707@codemonkey.ws>
	<20100804133401.GP10499@redhat.com>
	<4C5970AC.6060105@codemonkey.ws> <4C5995B4.90505@redhat.com>
	<4C5996F4.6010205@redhat.com> <4C5998F1.4030001@codemonkey.ws>
	<4C5A6839.2070700@redhat.com> <20100805073447.GH10499@redhat.com>
	<4C5A6EC4.2050007@redhat.com> <20100805075950.GI10499@redhat.com>
In-Reply-To: <20100805075950.GI10499@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, Gerd Hoffmann <kraxel@redhat.com>, "Richard W.M. Jones" <rjones@redhat.com>

  On 08/05/2010 10:59 AM, Gleb Natapov wrote:
>
>> We have the firmware configuration interface for that, if we can
>> tolerate its speed.
>>
> To pass default boot device, sure :) The question is what to pass so
> that seabios will be able to unambiguously determine what device to
> boot from.

IMO seabios should (if it doesn't already) store this information in 
CMOS non-volatile memory (which can be backed by a small disk image).  
This allows the user to play with the configuration at boot time, and if 
we document the format, management tools can read and write it as well.

-- 
error compiling committee.c: too many arguments to function