From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:41392) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQJ5g-0004bZ-Qc for qemu-devel@nongnu.org; Fri, 04 May 2012 10:02:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SQJ5a-0002B7-HV for qemu-devel@nongnu.org; Fri, 04 May 2012 10:02:36 -0400 Received: from e06smtp10.uk.ibm.com ([195.75.94.106]:49916) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQJ5a-0002Aq-9M for qemu-devel@nongnu.org; Fri, 04 May 2012 10:02:30 -0400 Received: from /spool/local by e06smtp10.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 4 May 2012 15:02:28 +0100 Received: from d06av06.portsmouth.uk.ibm.com (d06av06.portsmouth.uk.ibm.com [9.149.37.217]) by d06nrmr1507.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q44E2OYg2625720 for ; Fri, 4 May 2012 15:02:24 +0100 Received: from d06av06.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av06.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q44E28LI002983 for ; Fri, 4 May 2012 08:02:09 -0600 Message-ID: <4FA3E15D.20804@de.ibm.com> Date: Fri, 04 May 2012 16:02:05 +0200 From: Christian Borntraeger MIME-Version: 1.0 References: <1336139040-16628-1-git-send-email-borntraeger@de.ibm.com> <1336139040-16628-2-git-send-email-borntraeger@de.ibm.com> <16456C5E-6C77-4976-8F09-A122C0FE0943@suse.de> <4FA3E108.9040204@de.ibm.com> In-Reply-To: <4FA3E108.9040204@de.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/1] s390: IPL device for s390 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Cornelia Huck , Jens Freimann , Heinz Graalfs , qemu-devel On 04/05/12 16:00, Christian Borntraeger wrote: >>> An IPL (booting) on s390 of SCSI disks is done by a firmware component. >>> Lets implement this scheme as an qemu device that also allows to >>> configure the IPL like the HMC. We have a parameter iplid that >>> refers to a disk device and a load parm that specifies the entry >>> on the disk to be ipled. We also provide a default device >>> if no -device s390-ipl statement is given. >> >> Any reason we can't do this in guest firmware code? > > Conceptually guest firmware does not exist in the guest address space > on s390. It is separate in a storage area called HSA. > (you could say the existing hardware is semi-hosted, you cant buy it bare > metal. > Doing the boot code in guest address space will fail if the guest firmware > address collides with the addresses specified by a bootmap. Or in other words, this code is closer to the real s390 boxes.