From: David Hildenbrand <david@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Collin Walling <walling@linux.ibm.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org,
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 0/4] s390x/zpci: some hotplug handler cleanups
Date: Tue, 13 Nov 2018 13:06:47 +0100 [thread overview]
Message-ID: <84c46d77-4ebc-0754-de83-751aa7ed32dc@redhat.com> (raw)
In-Reply-To: <20181113100313.307711b0.cohuck@redhat.com>
On 13.11.18 10:03, Cornelia Huck wrote:
> On Mon, 12 Nov 2018 18:34:34 +0100
> David Hildenbrand <david@redhat.com> wrote:
>
>> On 12.11.18 18:14, Cornelia Huck wrote:
>>> On Mon, 5 Nov 2018 12:03:09 +0100
>>> David Hildenbrand <david@redhat.com> wrote:
>>>
>>>> The hotplug code needs more love, but let's do some obvious cleanups
>>>> first. In the future, we want to propery make use of unplug_request() +
>>>> unplug(), instead of routing everything (especially two separate but
>>>> linked) devices via a single unplug call. Also, we want to move all
>>>> errors in plug() into the pre_plug() handler, but this will require
>>>> general PCI refactorings (moving stuff from realize() to the pre_plug/plug
>>>> handler).
>>>>
>>>> This series is based on "[PATCH v2 00/10] pci: hotplug handler reworks",
>>>> which contains one cleanup for s390x.
>>>>
>>>> David Hildenbrand (4):
>>>> s390x/zpci: drop msix.available
>>>
>>> queued to s390-next
>>>
>>>> s390x/zpci: use hotplug_dev instead of looking up the host bridge
>>>
>>> Do we have consensus on that one yet? I can take it or leave it :)
>>>
>>>> s390x/zpci: move some hotplug checks to the pre_plug handler
>>>
>>> depends on the handler rework
>>
>> I can pull that one out from the general handler rework (still need
>> review either way so it could take a while).
>
> It's 4.0 material anyway, so no need to hurry.
>
>>
>>>
>>>> s390x/zpci: properly fail if the zPCI device cannot be created
>>>
>>> Waiting for a fixed patch... can queue to s390-fixes if it arrives
>>> soon(tm).
>>
>> Thanks!
>>
>> Shall I resend all or only this one?
>
> The last one would be great, as I think it's still 3.1 material.
>
Alrighty, so I'll resend (after testing this time ;) ) the last patch.
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2018-11-13 12:07 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 ` [Qemu-devel] [qemu-s390x] " Collin Walling
2018-11-07 19:36 ` 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 ` David Hildenbrand [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=84c46d77-4ebc-0754-de83-751aa7ed32dc@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@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 \
--cc=walling@linux.ibm.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).