From: Dinar Valeev <dvaleev@suse.de>
To: Gonglei <arei.gonglei@huawei.com>
Cc: "armbru@redhat.com" <armbru@redhat.com>,
Dinar Valeev <dvaleev@suse.com>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 2/2] bootdevice: update boot_order in MachineState
Date: Wed, 28 Jan 2015 23:22:01 +0100 [thread overview]
Message-ID: <54C96109.5060807@suse.de> (raw)
In-Reply-To: <54C83FD2.8050208@huawei.com>
On 01/28/2015 02:48 AM, Gonglei wrote:
> On 2015/1/27 18:49, Dinar Valeev wrote:
>
>> On 01/27/2015 10:18 AM, Gonglei wrote:
>>> On 2015/1/27 16:57, Dinar Valeev wrote:
>>>
>>>> On 01/27/2015 03:51 AM, Gonglei wrote:
>>>>> On 2015/1/27 7:52, dvaleev@suse.de wrote:
>>>>>
>>>>>> From: Dinar Valeev <dvaleev@suse.com>
>>>>>>
>>>>>> on sPAPR we need to update boot_order in MachineState in case it
>>>>>> got changed on reset.
>>>>>>
>>>>>> Signed-off-by: Dinar Valeev <dvaleev@suse.com>
>>>>>> ---
>>>>>> bootdevice.c | 3 +++
>>>>>> 1 file changed, 3 insertions(+)
>>>>>>
>>>>>> diff --git a/bootdevice.c b/bootdevice.c
>>>>>> index 5914417..4f11a06 100644
>>>>>> --- a/bootdevice.c
>>>>>> +++ b/bootdevice.c
>>>>>> @@ -26,6 +26,7 @@
>>>>>> #include "qapi/visitor.h"
>>>>>> #include "qemu/error-report.h"
>>>>>> #include "hw/hw.h"
>>>>>> +#include "hw/boards.h"
>>>>>>
>>>>>> typedef struct FWBootEntry FWBootEntry;
>>>>>>
>>>>>> @@ -50,6 +51,8 @@ void qemu_register_boot_set(QEMUBootSetHandler *func, void *opaque)
>>>>>> void qemu_boot_set(const char *boot_order, Error **errp)
>>>>>> {
>>>>>> Error *local_err = NULL;
>>>>>> + MachineState *machine = MACHINE(qdev_get_machine());
>>>>>> + machine->boot_order = boot_order;
>>>>>>
>>>>>> if (!boot_set_handler) {
>>>>>> error_setg(errp, "no function defined to set boot device list for"
>>>>>
>>>>> Have you registered boot set handler on ppc/sPAPR platform by calling
>>>>> qemu_register_boot_set()? Otherwise qemu_boot_set function
>>>>> will return error.
>>>> No, I set boot_order on each machine reset. My tests are showing it works without an error.
>>>
>>> That's interesting. Does this function be called?
>> Yes, then simply returns.
>>> Would you debug it by setting a breakpoint ?
>> I added a trace event.
>> if (!boot_set_handler) {
>> + trace_qemu_boot_set(boot_order);
>> error_setg(errp, "no function defined to set boot device list for"
>> " this architecture");
>> return;
>>
>> And I see this now in qemu's monitor. Still I don't see error message.
>
> That's because NULL is passed to this function in restore_boot_order()
> the error is ignored (commit f183993). I have seen the previous conversation
> about your patch serials. And I think this is the reason which
> you moved machine->boot_order = boot_order before
> checking boot_set_handler variable based on Alexander's
> suggestion, right? But I think this is not a good idea.
Yes
Any proposal how this can be done differently?
It seems I'm almost alone who wants -boot once=X option to get fixed for sPAPR. We use it in test automation, and we need to be sure that we boot from hard disk once installation is done.
Thanks,
Dinar
>
> Regards,
> -Gonglei
>
>
next prev parent reply other threads:[~2015-01-28 22:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 23:52 [Qemu-devel] Update boot_order on reset for sPAPR dvaleev
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 [this message]
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=54C96109.5060807@suse.de \
--to=dvaleev@suse.de \
--cc=agraf@suse.de \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=dvaleev@suse.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).