From: Collin Walling <walling@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@redhat.com>, Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, Thomas Huth <thuth@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH v1 3/4] s390x/zpci: move some hotplug checks to the pre_plug handler
Date: Wed, 7 Nov 2018 14:34:53 -0500 [thread overview]
Message-ID: <723f6454-8cac-08ed-bdb6-afddc4ed7ad1@linux.ibm.com> (raw)
In-Reply-To: <228ec0b2-cd30-b33b-8120-bb28e3f83e66@redhat.com>
On 11/5/18 6:50 AM, David Hildenbrand wrote:
> On 05.11.18 12:03, David Hildenbrand wrote:
>> Let's move most of the checks to the new pre_plug handler. As a PCI
>> bridge is just a PCI device, we can simplify the code.
>>
>> Notes: We cannot yet move the MSIX check or device ID creation +
>> zPCI device creation to the pre_plug handler as both parts are not
>> fixed before actual device realization (and therefore after pre_plug and
>> before plug). Once that part is factored out, we can move these parts to
>> the pre_plug handler, too and therefore remove all possible errors from
>> the plug handler.
>>
>> Signed-off-by: David Hildenbrand <david@redhat.com>
>> ---
>> hw/s390x/s390-pci-bus.c | 43 +++++++++++++++++++++++++----------------
>> 1 file changed, 26 insertions(+), 17 deletions(-)
>>
>> diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
>> index 68660eac74..1849f9d334 100644
>> --- a/hw/s390x/s390-pci-bus.c
>> +++ b/hw/s390x/s390-pci-bus.c
>> @@ -806,11 +806,31 @@ static bool s390_pci_alloc_idx(S390pciState *s, S390PCIBusDevice *pbdev)
>> }
>>
>> pbdev->idx = idx;
>> - s->next_idx = (idx + 1) & FH_MASK_INDEX;
>> -
>> return true;
>> }
>>
>> +static void s390_pcihost_pre_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
>> + Error **errp)
>> +{
>> + S390pciState *s = S390_PCI_HOST_BRIDGE(hotplug_dev);
>> +
>> + if (object_dynamic_cast(OBJECT(dev), TYPE_PCI_DEVICE)) {
>> + PCIDevice *pdev = PCI_DEVICE(dev);
>> +
>> + if (pdev->cap_present & QEMU_PCI_CAP_MULTIFUNCTION) {
>> + error_setg(errp, "multifunction not supported in s390");
>> + return;
>> + }
>> + } else if (object_dynamic_cast(OBJECT(dev), TYPE_S390_PCI_DEVICE)) {
>> + S390PCIBusDevice *pbdev = S390_PCI_DEVICE(dev);
>> +
>> + if (!s390_pci_alloc_idx(s, pbdev)) {
>> + error_setg(errp, "no slot for plugging zpci device");
>> + return;
>> + }
>> + }
>> +}
>> +
>> static void s390_pcihost_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
>> Error **errp)
>> {
>> @@ -823,11 +843,6 @@ static void s390_pcihost_plug(HotplugHandler *hotplug_dev, DeviceState *dev,>> PCIBridge *pb = PCI_BRIDGE(dev);
>> PCIDevice *pdev = PCI_DEVICE(dev);
>>
>> - if (pdev->cap_present & QEMU_PCI_CAP_MULTIFUNCTION) {
>> - error_setg(errp, "multifunction not supported in s390");
>> - return;
>> - }
>> -
>> pci_bridge_map_irq(pb, dev->id, s390_pci_map_irq);
>> pci_setup_iommu(&pb->sec_bus, s390_pci_dma_iommu, s);
>>
>> @@ -847,11 +862,6 @@ static void s390_pcihost_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
>> } else if (object_dynamic_cast(OBJECT(dev), TYPE_PCI_DEVICE)) {
>> pdev = PCI_DEVICE(dev);
>>
>> - if (pdev->cap_present & QEMU_PCI_CAP_MULTIFUNCTION) {
>> - error_setg(errp, "multifunction not supported in s390");
>> - return;
>> - }
>> -
>> if (!dev->id) {
>> /* In the case the PCI device does not define an id */
>> /* we generate one based on the PCI address */
>> @@ -883,7 +893,7 @@ static void s390_pcihost_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
>>
>> if (s390_pci_msix_init(pbdev)) {
>> error_setg(errp, "MSI-X support is mandatory "
>> - "in the S390 architecture");
>> + "in the S390 architecture");
>
> I will drop this unrelated change.
>
>> return;
>> }
>>
>> @@ -894,10 +904,8 @@ static void s390_pcihost_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
>> } else if (object_dynamic_cast(OBJECT(dev), TYPE_S390_PCI_DEVICE)) {
>> pbdev = S390_PCI_DEVICE(dev);
>>
>> - if (!s390_pci_alloc_idx(s, pbdev)) {
>> - error_setg(errp, "no slot for plugging zpci device");
>> - return;
>> - }
>> + /* the allocated idx is actually getting used */
>> + s->next_idx = (pbdev->idx + 1) & FH_MASK_INDEX;
>> pbdev->fh = pbdev->idx;
>> QTAILQ_INSERT_TAIL(&s->zpci_devs, pbdev, link);
>> g_hash_table_insert(s->zpci_table, &pbdev->idx, pbdev);
>> @@ -1030,6 +1038,7 @@ static void s390_pcihost_class_init(ObjectClass *klass, void *data)
>>
>> dc->reset = s390_pcihost_reset;
>> dc->realize = s390_pcihost_realize;
>> + hc->pre_plug = s390_pcihost_pre_plug;
>> hc->plug = s390_pcihost_plug;
>> hc->unplug = s390_pcihost_unplug;
>> msi_nonbroken = true;
>>
When did these function names drop the *_hot_plug postfix? Latest master does not reflect this change for me.
Just figured I'd mention it now in case merging becomes a pain later ;)
>
>
The above concerns do not relate to any functionality of the code, so with them addressed, then:
Reviewed-by: Collin Walling <walling@linux.ibm.com>
--
Respectfully,
- Collin Walling
next prev parent reply other threads:[~2018-11-07 19:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 11:03 [Qemu-devel] [PATCH v1 0/4] s390x/zpci: some hotplug handler cleanups David Hildenbrand
2018-11-05 11:03 ` [Qemu-devel] [PATCH v1 1/4] s390x/zpci: drop msix.available David Hildenbrand
2018-11-05 11:19 ` Cornelia Huck
2018-11-07 16:26 ` [Qemu-devel] [qemu-s390x] " Collin Walling
2018-11-08 10:54 ` Cornelia Huck
2018-11-05 11:25 ` [Qemu-devel] " Thomas Huth
2018-11-12 17:12 ` Cornelia Huck
2018-11-05 11:03 ` [Qemu-devel] [PATCH v1 2/4] s390x/zpci: use hotplug_dev instead of looking up the host bridge David Hildenbrand
2018-11-05 11:21 ` Cornelia Huck
2018-11-05 11:37 ` David Hildenbrand
2018-11-05 11:40 ` Christian Borntraeger
2018-11-05 11:50 ` David Hildenbrand
2018-11-07 20:28 ` Collin Walling
2018-11-08 11:07 ` Cornelia Huck
2018-11-08 11:56 ` David Hildenbrand
2018-11-05 11:03 ` [Qemu-devel] [PATCH v1 3/4] s390x/zpci: move some hotplug checks to the pre_plug handler David Hildenbrand
2018-11-05 11:50 ` David Hildenbrand
2018-11-07 19:34 ` Collin Walling [this message]
2018-11-07 19:36 ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2018-11-07 19:46 ` Collin Walling
2018-11-05 11:03 ` [Qemu-devel] [PATCH v1 4/4] s390x/zpci: properly fail if the zPCI device cannot be created David Hildenbrand
2018-11-05 12:04 ` Thomas Huth
2018-11-05 12:41 ` Cornelia Huck
2018-11-05 12:46 ` David Hildenbrand
2018-11-08 11:14 ` Cornelia Huck
2018-11-07 20:15 ` Collin Walling
2018-11-08 13:35 ` Cornelia Huck
2018-11-08 13:58 ` David Hildenbrand
2018-11-12 17:14 ` [Qemu-devel] [PATCH v1 0/4] s390x/zpci: some hotplug handler cleanups Cornelia Huck
2018-11-12 17:34 ` David Hildenbrand
2018-11-13 9:03 ` Cornelia Huck
2018-11-13 12:06 ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
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=723f6454-8cac-08ed-bdb6-afddc4ed7ad1@linux.ibm.com \
--to=walling@linux.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
/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).