From: Janne Huttunen <janne.huttunen@nokia.com>
To: Laszlo Ersek <lersek@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Cc: "kraxel@redhat.com" <kraxel@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property
Date: Thu, 23 Mar 2017 08:53:04 +0200 [thread overview]
Message-ID: <1490251984.25746.15.camel@nokia.com> (raw)
In-Reply-To: <3229b3f8-7689-94d1-05a8-8b8c34bc0d25@redhat.com>
On Wed, 2017-03-22 at 16:29 +0100, Laszlo Ersek wrote:
> > I'm not. I'm using QMP to change the index dynamically.
> >
> Wait, if you are already changing the "bootindex" property
> dynamically (do I understand that right?)
No, I'm not changing "bootindex" dynamically. I'm changing
"bootonceindex" dynamically. The point is that whatever
change I'm making is supposed to affect only one boot, the
next one. Since the guest can trigger reboots by itself,
I don't necessarily know when they are going to happen.
Like I said earlier, I can get very close to the semantics
I need if set the "bootindex" and get an event when the
boot happens so that I know when to reset the bootindex
back to the original value. However doing it like that
is (at least in theory) racy if the event isn't synchronous
and it requires some process that actively monitors those
events which I'm trying to avoid.
> ...and it could have a significant maintenance footprint,
> while the feature does look niche (to me anyway).
Whatever I'm currently doing is definitely a niche, but very
similar setting of a one time boot source while the system
is running is e.g. part of the IPMI standard (see "Set
System Boot Options Command" in IPMI Specification), so
the concept itself is not that much of a niche.
next prev parent reply other threads:[~2017-03-23 7:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 12:50 [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 1/6] Re-factor bootdevice list handling, pt1 Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 2/6] Re-factor bootdevice list handling, pt2 Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 3/6] Add support for "bootonceindex" property Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 4/6] Clear the boot once list after it has been used Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 5/6] Support "bootonceindex" property for virtio-net interfaces Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 6/6] Support "bootonceindex" property for SCSI disks Janne Huttunen
2017-03-14 16:57 ` [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property Gerd Hoffmann
2017-03-15 6:58 ` Janne Huttunen
2017-03-15 7:24 ` Gerd Hoffmann
2017-03-16 9:46 ` Janne Huttunen
2017-03-16 9:59 ` Gerd Hoffmann
2017-03-21 17:48 ` Eric Blake
2017-03-22 5:42 ` Markus Armbruster
2017-03-21 17:55 ` Paolo Bonzini
2017-03-22 6:36 ` Janne Huttunen
2017-03-22 8:43 ` Paolo Bonzini
2017-03-22 9:00 ` Huttunen, Janne (Nokia - FI/Espoo)
2017-03-22 10:51 ` Laszlo Ersek
2017-03-22 13:58 ` Janne Huttunen
2017-03-22 14:36 ` Laszlo Ersek
2017-03-22 15:19 ` Janne Huttunen
2017-03-22 15:29 ` Laszlo Ersek
2017-03-23 6:53 ` Janne Huttunen [this message]
2017-03-23 9:13 ` Laszlo Ersek
[not found] ` <CACaajQsrkuZeC6WYXdEBJY=FEkTQ9iY_i8E-d5j7JqK5DDUuOw@mail.gmail.com>
2017-03-15 7:21 ` Vasiliy Tolstov
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=1490251984.25746.15.camel@nokia.com \
--to=janne.huttunen@nokia.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.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.