All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
	pkrempa@redhat.com, qemu-block@nongnu.org, mst@redhat.com,
	philmd@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com,
	marcandre.lureau@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
	lersek@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 11/12] pc: Support firmware configuration with -blockdev
Date: Tue, 12 Mar 2019 07:52:38 +0100	[thread overview]
Message-ID: <87ef7c7fex.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAAdtpL5FQS+bBxHT0mvNv8gxiaRUVeZHZFBc-e11agS2majRiw@mail.gmail.com> ("Philippe =?utf-8?Q?Mathieu-Daud=C3=A9=22's?= message of "Mon, 11 Mar 2019 18:18:17 +0100")

Philippe Mathieu-Daudé <f4bug@amsat.org> writes:

> Le lun. 11 mars 2019 17:02, Markus Armbruster <armbru@redhat.com> a écrit :
>
>> Paolo Bonzini <pbonzini@redhat.com> writes:
[...]
>> > Does it work if you add the device yourself as a child of /machine,
>> > instead of relying on /machine/unattached?
>>
>> I figure you're suggesting something like this incremental patch:
>>
>>    diff --git a/hw/i386/pc_sysfw.c b/hw/i386/pc_sysfw.c
>>    index ccf2221acb..9d3a80c51a 100644
>>    --- a/hw/i386/pc_sysfw.c
>>    +++ b/hw/i386/pc_sysfw.c
>>    @@ -99,6 +99,10 @@ void pc_system_flash_create(PCMachineState *pcms)
>>         if (pcmc->pci_enabled) {
>>             pcms->flash[0] = pc_pflash_create("system.flash0");
>>             pcms->flash[1] = pc_pflash_create("system.flash1");
>>    +        object_property_add_child(OBJECT(pcms), "pfl0",
>>    +                                  OBJECT(pcms->flash[0]),
>> &error_abort);
>>    +        object_property_add_child(OBJECT(pcms), "pfl1",
>>    +                                  OBJECT(pcms->flash[1]),
>> &error_abort);
>>             object_property_add_alias(OBJECT(pcms), "pflash0",
>>                                       OBJECT(pcms->flash[0]), "drive",
>>                                       &error_abort);
>>    @@ -122,19 +126,7 @@ static void
>> pc_system_flash_cleanup_unused(PCMachineState *pcms)
>>                 prop_name = g_strdup_printf("pflash%d", i);
>>                 object_property_del(OBJECT(pcms), prop_name, &error_abort);
>>                 g_free(prop_name);
>>    -            /*
>>    -             * Delete @dev_obj.  Straight object_unref() is wrong,
>>    -             * since it leaves dangling references in the parent bus
>>    -             * behind.  object_unparent() doesn't work, either: since
>>    -             * @dev_obj hasn't been realized, dev_obj->parent is null,
>>    -             * and object_unparent() does nothing.  DeviceClass method
>>    -             * device_unparent() works, but we have to take a
>>    -             * temporary reference, or else device_unparent() commits
>>    -             * a use-after-free error.
>>    -             */
>>    -            object_ref(dev_obj);
>>    -            object_get_class(dev_obj)->unparent(dev_obj);
>>    -            object_unref(dev_obj);
>>    +            object_unparent(dev_obj);
>>                 pcms->flash[i] = NULL;
>>             }
>>         }
>>
>> Passes "make check" and "info qtree" looks good both with and without
>> -machine pflash0,...
>>
>> I'm not exactly happy with "pfl0" and "pfl1".  Got a favorite color for
>> my bikeshed?
>>
>
> ovmf_code & ovmf_vars?

Tempting, since we use these guys only for OVMF so far.  However, we
could also use them for SeaBIOS[*], or whatever other firmware comes up.

[...]


[*] See also
Subject: Re: Configuring pflash devices for OVMF firmware
Message-ID: <9c4e222f-3941-426e-3195-5598b2af1501@redhat.com>
https://lists.nongnu.org/archive/html/qemu-devel/2019-01/msg08145.html

  reply	other threads:[~2019-03-12  7:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 13:14 [Qemu-devel] [PATCH v3 00/12] pc: Support firmware configuration with -blockdev Markus Armbruster
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 01/12] qdev: Fix latent bug with compat_props and onboard devices Markus Armbruster
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 02/12] qom: Move compat_props machinery from qdev to QOM Markus Armbruster
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 03/12] vl: Fix latent bug with -global and onboard devices Markus Armbruster
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 04/12] sysbus: Fix latent bug with " Markus Armbruster
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 05/12] vl: Improve legibility of BlockdevOptions queue Markus Armbruster
2019-03-08 14:48   ` Philippe Mathieu-Daudé
2019-03-11 14:17   ` Paolo Bonzini
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 06/12] vl: Factor configure_blockdev() out of main() Markus Armbruster
2019-03-11 14:18   ` Paolo Bonzini
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 07/12] vl: Create block backends before setting machine properties Markus Armbruster
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 08/12] pflash_cfi01: Add pflash_cfi01_get_blk() helper Markus Armbruster
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 09/12] pc_sysfw: Remove unused PcSysFwDevice Markus Armbruster
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 10/12] pc_sysfw: Pass PCMachineState to pc_system_firmware_init() Markus Armbruster
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 11/12] pc: Support firmware configuration with -blockdev Markus Armbruster
2019-03-11 14:30   ` Paolo Bonzini
2019-03-11 15:42     ` Markus Armbruster
2019-03-11 17:08       ` Paolo Bonzini
2019-03-11 17:18       ` Philippe Mathieu-Daudé
2019-03-12  6:52         ` Markus Armbruster [this message]
2019-03-08 13:14 ` [Qemu-devel] [PATCH v3 12/12] docs/interop/firmware.json: Prefer -machine to if=pflash Markus Armbruster
2019-03-08 13:38   ` Laszlo Ersek
2019-03-08 13:41 ` [Qemu-devel] [PATCH v3 00/12] pc: Support firmware configuration with -blockdev Michael S. Tsirkin
2019-03-08 14:39   ` Markus Armbruster
2019-03-11 17:39 ` [Qemu-devel] [PATCH v4 11/12] " Markus Armbruster
2019-03-11 17:42   ` Markus Armbruster
2019-03-11 17:45     ` Paolo Bonzini

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=87ef7c7fex.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=kwolf@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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.