From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Heinz Graalfs <graalfs@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/1] s390: IPL device for s390
Date: Fri, 04 May 2012 16:00:40 +0200 [thread overview]
Message-ID: <4FA3E108.9040204@de.ibm.com> (raw)
In-Reply-To: <16456C5E-6C77-4976-8F09-A122C0FE0943@suse.de>
On 04/05/12 15:53, Alexander Graf wrote:
>
> On 04.05.2012, at 15:44, 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.
Christian
next prev parent reply other threads:[~2012-05-04 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 13:43 [Qemu-devel] [PATCH 0/1] RFC: ipl device for s390 Christian Borntraeger
2012-05-04 13:44 ` [Qemu-devel] [PATCH 1/1] s390: IPL " Christian Borntraeger
2012-05-04 13:53 ` Alexander Graf
2012-05-04 14:00 ` Christian Borntraeger [this message]
2012-05-04 14:02 ` Christian Borntraeger
2012-05-04 18:12 ` Alexander Graf
2012-05-08 12:32 ` Christian Borntraeger
2012-05-08 12:40 ` Alexander Graf
2012-05-08 14:43 ` Christian Borntraeger
2012-05-08 14:53 ` Alexander Graf
2012-05-08 18:54 ` Christian Borntraeger
2012-05-08 19:18 ` Alexander Graf
2012-05-08 19:16 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FA3E108.9040204@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=graalfs@linux.vnet.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.