From: Marcel Apfelbaum <marcel.a@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: marcel@redhat.com, pbonzini@redhat.com,
alex.williamson@redhat.com, qemu-devel@nongnu.org,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 2/2] hw/pci: fixed hotplug crash when using rombar=0 with devices having romfile
Date: Mon, 03 Nov 2014 15:49:28 +0200 [thread overview]
Message-ID: <1415022568.2327.34.camel@localhost.localdomain> (raw)
In-Reply-To: <877fzcwgfm.fsf@blackfin.pond.sub.org>
On Mon, 2014-11-03 at 14:40 +0100, Markus Armbruster wrote:
> Marcel Apfelbaum <marcel.a@redhat.com> writes:
>
> > On Mon, 2014-11-03 at 13:03 +0100, Markus Armbruster wrote:
> >> Marcel Apfelbaum <marcel.a@redhat.com> writes:
> >>
> >> > Hot-plugging a device that has a romfile (either supplied by user
> >> > or built-in) using rombar=0 option is a user error,
> >> > do not allow the device to be hot-plugged.
> >> >
> >> > Reviewed-by: Eric Blake <eblake@redhat.com>
> >> > Signed-off-by: Marcel Apfelbaum <marcel.a@redhat.com>
> >> > ---
> >> > hw/pci/pci.c | 9 +++++++++
> >> > 1 file changed, 9 insertions(+)
> >> >
> >> > diff --git a/hw/pci/pci.c b/hw/pci/pci.c
> >> > index 36226eb..371699c 100644
> >> > --- a/hw/pci/pci.c
> >> > +++ b/hw/pci/pci.c
> >> > @@ -1942,6 +1942,15 @@ static int pci_add_option_rom(PCIDevice *pdev, bool is_default_rom)
> >> > * for 0.11 compatibility.
> >> > */
> >> > int class = pci_get_word(pdev->config + PCI_CLASS_DEVICE);
> >> > +
> >> > + /*
> >> > + * Hot-plugged devices can't use the option ROM
> >> > + * if the rom bar is disabled.
> >> > + */
> >> > + if (DEVICE(pdev)->hotplugged) {
> >> > + return -1;
> >> > + }
> >> > +
> >> > if (class == 0x0300) {
> >> > rom_add_vga(pdev->romfile);
> >> > } else {
> >>
> >> Unlike the function's other unsuccessful returns, this one is silent.
> >> Intentional?
> > Yes, the first version included an error message, but was not accepted
> > as the reviewers preferred "silent drop" instead.
> > The main reason was that a proper error propagation mechanism
> > should be used.
> > At the time of the patch there was not such an option, but now there is.
> > I can add it on top of your series, preferably after is merged.
>
> My rebased "pci: Convert core to realize" has this hunk:
>
> @@ -1948,7 +1955,9 @@ static int pci_add_option_rom(PCIDevice *pdev, bool is_default_rom)
> * if the rom bar is disabled.
> */
> if (DEVICE(pdev)->hotplugged) {
> - return -1;
> + error_setg(errp, "Hot-plugged device without ROM bar"
> + " can't have an option ROM");
> + return;
> }
>
> if (class == 0x0300) {
>
> Bad, because the patch does two separate things: fix a failure not to be
> silent, and convert to realize. Needs to be split. Begs the question
> how to order the parts. I'd prefer to put the fix first, and get it
> into 2.2. What do you think?
If I understand your question correctly:
I would first convert to realize, then add the fix.
The reason for it is pretty simple: Conversion to realize
gives us the error flow propagation we need.
Thanks,
Marcel
next prev parent reply other threads:[~2014-11-03 13:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 17:34 [Qemu-devel] [PATCH v4 0/2] hw/pci: fixed hotplug crash when using rombar=0 with devices having romfile Marcel Apfelbaum
2014-10-27 17:34 ` [Qemu-devel] [PATCH v4 1/2] hw/pci: fixed error flow in pci_qdev_init Marcel Apfelbaum
2014-10-30 13:33 ` Markus Armbruster
2014-10-30 17:25 ` Marcel Apfelbaum
2014-10-27 17:34 ` [Qemu-devel] [PATCH v4 2/2] hw/pci: fixed hotplug crash when using rombar=0 with devices having romfile Marcel Apfelbaum
2014-11-03 12:03 ` Markus Armbruster
2014-11-03 12:46 ` Michael S. Tsirkin
2014-11-03 12:52 ` Marcel Apfelbaum
2014-11-03 13:40 ` Markus Armbruster
2014-11-03 13:49 ` Marcel Apfelbaum [this message]
2014-11-03 15:54 ` Markus Armbruster
2014-11-03 16:07 ` Marcel Apfelbaum
2014-11-03 16:10 ` Michael S. Tsirkin
2014-11-24 15:22 ` [Qemu-devel] [PATCH v4 0/2] " Marcel Apfelbaum
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=1415022568.2327.34.camel@localhost.localdomain \
--to=marcel.a@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@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 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).