From: dvaleev@suse.de
To: qemu-devel@nongnu.org
Cc: Gonglei <arei.gonglei@huawei.com>,
qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
armbru@redhat.com
Subject: [Qemu-devel] Update boot_order on reset for sPAPR
Date: Tue, 27 Jan 2015 00:52:19 +0100 [thread overview]
Message-ID: <1422316341-28983-1-git-send-email-dvaleev@suse.de> (raw)
This is cleaner attempt to fix -boot once=X behaviour on sPAPR
qemu-system-ppc64 -m 1024 -enable-kvm -boot once=d -vga none -nographic
Ready!
0 > dev /chosen ok
0 > .properties
stdout 3e512100
....
ibm,architecture-vec-5 00000000 0080
qemu,boot-device d
6400
linux,stdout-path /vdevice/vty@71000000
....
0 > reset-all
....
Ready!
0 > dev /chosen ok
0 > .properties
stdout 3e512100
....
ibm,architecture-vec-5 00000000 0080
linux,stdout-path /vdevice/vty@71000000
Compared to previous patch set, this one doesn't implement register_boot_set for sPAPR,
but instead updates boot_order at MachineState and read it on each guest's reset.
next reply other threads:[~2015-01-26 23:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 23:52 dvaleev [this message]
2015-01-26 23:52 ` [Qemu-devel] [PATCH 1/2] sPAPR: reread boot_device on reset dvaleev
2015-01-26 23:52 ` [Qemu-devel] [PATCH 2/2] bootdevice: update boot_order in MachineState dvaleev
2015-01-27 2:51 ` Gonglei
2015-01-27 8:57 ` Dinar Valeev
2015-01-27 9:18 ` Gonglei
2015-01-27 9:56 ` Dinar Valeev
2015-01-27 10:49 ` Dinar Valeev
2015-01-28 1:48 ` Gonglei
2015-01-28 22:22 ` Dinar Valeev
2015-01-29 0:41 ` Gonglei
2015-01-29 7:48 ` Markus Armbruster
2015-01-29 10:53 ` Alexander Graf
2015-01-29 10:55 ` Alexander Graf
2015-01-29 11:08 ` Gonglei
2015-01-29 11:11 ` Alexander Graf
2015-01-27 2:31 ` [Qemu-devel] Update boot_order on reset for sPAPR Alexey Kardashevskiy
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=1422316341-28983-1-git-send-email-dvaleev@suse.de \
--to=dvaleev@suse.de \
--cc=agraf@suse.de \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).