From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Julia Suvorova <jusual@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH] hw/pci/pcie: Move hot plug capability check to pre_plug callback
Date: Thu, 4 Jun 2020 07:14:11 -0400 [thread overview]
Message-ID: <20200604071341-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200604125755.12944ac4@redhat.com>
On Thu, Jun 04, 2020 at 12:57:55PM +0200, Igor Mammedov wrote:
> On Mon, 1 Jun 2020 18:29:34 +0200
> Julia Suvorova <jusual@redhat.com> wrote:
>
> > Check for hot plug capability earlier to avoid removing devices attached
> > during the initialization process.
> >
> > Run qemu with an unattached drive:
> > -drive file=$FILE,if=none,id=drive0 \
> > -device pcie-root-port,id=rp0,slot=3,bus=pcie.0,hotplug=off
> > Hotplug a block device:
> > device_add virtio-blk-pci,id=blk0,drive=drive0,bus=rp0
> > If hotplug fails on plug_cb, drive0 will be deleted.
> >
> > Signed-off-by: Julia Suvorova <jusual@redhat.com>
> > ---
> > Hard to say if it's a bug or generally acceptable behaviour, but seems like
> > hotplug_handler_plug should never fail.
>
> _unplug shouldn't fail the rest are allowed to, but it's hard to unwind
> intialization cleanly to _plug stage so if it's possible to do checks
> at _pre_plug time (i.e. before device's realize() is called) we should do so.
>
> Acked-by: Igor Mammedov <imammedo@redhat.com>
Makes sense. Julia could you repost with a tweaked commit log
and I'll apply. Thanks!
> >
> > hw/pci/pcie.c | 19 +++++++++++--------
> > 1 file changed, 11 insertions(+), 8 deletions(-)
> >
> > diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
> > index f50e10b8fb..5b9c022d91 100644
> > --- a/hw/pci/pcie.c
> > +++ b/hw/pci/pcie.c
> > @@ -407,6 +407,17 @@ static void pcie_cap_slot_plug_common(PCIDevice *hotplug_dev, DeviceState *dev,
> > void pcie_cap_slot_pre_plug_cb(HotplugHandler *hotplug_dev, DeviceState *dev,
> > Error **errp)
> > {
> > + PCIDevice *hotplug_pdev = PCI_DEVICE(hotplug_dev);
> > + uint8_t *exp_cap = hotplug_pdev->config + hotplug_pdev->exp.exp_cap;
> > + uint32_t sltcap = pci_get_word(exp_cap + PCI_EXP_SLTCAP);
> > +
> > + /* Check if hot-plug is disabled on the slot */
> > + if (dev->hotplugged && (sltcap & PCI_EXP_SLTCAP_HPC) == 0) {
> > + error_setg(errp, "Hot-plug failed: unsupported by the port device '%s'",
> > + DEVICE(hotplug_pdev)->id);
> > + return;
> > + }
> > +
> > pcie_cap_slot_plug_common(PCI_DEVICE(hotplug_dev), dev, errp);
> > }
> >
> > @@ -415,7 +426,6 @@ void pcie_cap_slot_plug_cb(HotplugHandler *hotplug_dev, DeviceState *dev,
> > {
> > PCIDevice *hotplug_pdev = PCI_DEVICE(hotplug_dev);
> > uint8_t *exp_cap = hotplug_pdev->config + hotplug_pdev->exp.exp_cap;
> > - uint32_t sltcap = pci_get_word(exp_cap + PCI_EXP_SLTCAP);
> > PCIDevice *pci_dev = PCI_DEVICE(dev);
> >
> > /* Don't send event when device is enabled during qemu machine creation:
> > @@ -431,13 +441,6 @@ void pcie_cap_slot_plug_cb(HotplugHandler *hotplug_dev, DeviceState *dev,
> > return;
> > }
> >
> > - /* Check if hot-plug is disabled on the slot */
> > - if ((sltcap & PCI_EXP_SLTCAP_HPC) == 0) {
> > - error_setg(errp, "Hot-plug failed: unsupported by the port device '%s'",
> > - DEVICE(hotplug_pdev)->id);
> > - return;
> > - }
> > -
> > /* To enable multifunction hot-plug, we just ensure the function
> > * 0 added last. When function 0 is added, we set the sltsta and
> > * inform OS via event notification.
prev parent reply other threads:[~2020-06-04 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 16:29 [PATCH] hw/pci/pcie: Move hot plug capability check to pre_plug callback Julia Suvorova
2020-06-02 3:54 ` Michael S. Tsirkin
2020-06-02 7:16 ` Julia Suvorova
2020-06-04 10:57 ` Igor Mammedov
2020-06-04 11:14 ` Michael S. Tsirkin [this message]
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=20200604071341-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=imammedo@redhat.com \
--cc=jusual@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).