All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Gonglei <arei.gonglei@huawei.com>
Cc: "Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	"dvaleev@suse.de" <dvaleev@suse.de>,
	Alexander Graf <agraf@suse.de>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] bootdevice: add check in restore_boot_order()
Date: Fri, 30 Jan 2015 08:46:00 +0100	[thread overview]
Message-ID: <87386syamf.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <54CAD48A.5020709@huawei.com> (Gonglei's message of "Fri, 30 Jan 2015 08:47:06 +0800")

Gonglei <arei.gonglei@huawei.com> writes:

> On 2015/1/30 0:03, Alexander Graf wrote:
>
>> 
>> 
>> On 29.01.15 14:29, arei.gonglei@huawei.com wrote:
>>> From: Gonglei <arei.gonglei@huawei.com>
>>>
>>> If boot order is invaild or is set failed,
>>> exit qemu.
>>>
>>> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
>> 
>> Do we really want to kill the machine only because the boot device
>> string doesn't validate?
>> 
>
> Not all of the situation. If people want to change boot order by qmp/hmp
> command, it just report an error, please see do_boot_set(). But if the boot
> order is set in qemu command line, it will exit qemu if the boot device string
> is invalidate, as this patch's situation, which follow the original processing
> way (commit ef3adf68).

I think Alex isn't concerned about the monitor command, but what happens
when boot order "once" is reset to "order" on system reset.

-boot errors should have been detected during command line processing
(strongly preferred) or initial startup (acceptable).  Detecting
configuration errors during operation is nasty.  In cases where we can't
avoid it (and I'm not sure this is one), we need to consider very
carefully whether the error should be fatal.

  reply	other threads:[~2015-01-30  7:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 13:29 [Qemu-devel] [PATCH 0/2] bootdevice: two little changes arei.gonglei
2015-01-29 13:29 ` [Qemu-devel] [PATCH 1/2] bootdevice: remove the check about boot_set_handler arei.gonglei
2015-01-29 16:03   ` Alexander Graf
2015-01-29 13:29 ` [Qemu-devel] [PATCH 2/2] bootdevice: add check in restore_boot_order() arei.gonglei
2015-01-29 16:03   ` Alexander Graf
2015-01-30  0:47     ` Gonglei
2015-01-30  7:46       ` Markus Armbruster [this message]
2015-01-30  8:20         ` Gonglei
2015-01-30 12:01           ` Markus Armbruster
2015-01-30 12:10             ` Gonglei
2015-01-30 12:32               ` Markus Armbruster
2015-01-30 12:43                 ` Gonglei
2015-02-02  9:37                   ` Markus Armbruster
2015-02-03  1:47                     ` Gonglei
2015-02-03  7:49                       ` Markus Armbruster
2015-02-03  8:52                         ` Gonglei

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=87386syamf.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=agraf@suse.de \
    --cc=arei.gonglei@huawei.com \
    --cc=dvaleev@suse.de \
    --cc=peter.huangpeng@huawei.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.