From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH 1/2] qemu-kvm: extboot: Keep variables in RAM Date: Fri, 19 Feb 2010 18:44:19 +0100 Message-ID: <4B7ECDF3.1080502@siemens.com> References: <4B7D6725.1090202@siemens.com> <4B7DA2C4.9040207@codemonkey.ws> <4B7DC5A5.5020500@linux.intel.com> <4B7E628E.2050107@siemens.com> <4B7EC149.5080603@linux.intel.com> <4B7EC46C.4090909@siemens.com> <4B7EC949.4080701@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , "Kevin O'Connor" , Avi Kivity , Marcelo Tosatti , kvm To: "H. Peter Anvin" Return-path: Received: from goliath.siemens.de ([192.35.17.28]:18927 "EHLO goliath.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753768Ab0BSRpB (ORCPT ); Fri, 19 Feb 2010 12:45:01 -0500 In-Reply-To: <4B7EC949.4080701@linux.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: H. Peter Anvin wrote: > Jan Kiszka wrote: >> Actually, I'm still in favor of proper (Sea)BIOS support for virtio and >> scsi, either via the paravirt port 0x405 and its qemu backend or via >> minimalistic support of the hardware directly in the BIOS. That would >> free us from all those hooking and unhooking dances at least. >> > > The *proper* thing is to support BBS in SeaBIOS - that way your device > drivers just hook in through the standard BEV/BCV mechanism (which > should be used by *all* the device drivers, including the internal ones.) If there is standard for this, even better. On first glance, it doesn't look like a specification monster. Still some work to do. Or are there already activities in this direction? If not let us fix the issue ad-hoc until we have full BBS. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux