All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
	Collin Walling <walling@linux.ibm.com>,
	Thomas Huth <thuth@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 0/6] s390x/pci: hotplug handler fixes and reworks
Date: Wed, 16 Jan 2019 11:19:04 +0100	[thread overview]
Message-ID: <20190116111904.6ebd749f.cohuck@redhat.com> (raw)
In-Reply-To: <20190114103110.10909-1-david@redhat.com>

On Mon, 14 Jan 2019 11:31:04 +0100
David Hildenbrand <david@redhat.com> wrote:

> A bunch of fixes and reworks for s390x/pci hotplug infrastructure.
> 
> Patch 1,2: Reworks already posted (pre_plug handler)
> Patch 3,4: Fixes for memory leaks
> Patch 5: Rework unplug handler (introduce unplug_request handler) which
>          also fixes some unplug scenarios
> Patch 6: Handle leftover unplug requests on reset
> 
> We might decide to drop 1. 3 and 4 can be picked up independently.

1-4 all have been reviewed, so I went ahead and picked them up.

> 
> v1 -> v2:
> - Some rewordings in patch descriptions
> - "s390x/pci: Introduce unplug requests and split unplug handler"
> -- Some simplifications regarding s390_pci_perform_unplug()
> 
> David Hildenbrand (6):
>   s390x/pci: Use hotplug_dev instead of looking up the host bridge
>   s390x/pci: Move some hotplug checks to the pre_plug handler
>   s390x/pci: Always delete and free the release_timer
>   s390x/pci: Ignore the unplug call if we already have a release_timer
>   s390x/pci: Introduce unplug requests and split unplug handler
>   s390x/pci: Unplug remaining devices on pcihost reset
> 
>  hw/s390x/s390-pci-bus.c | 215 +++++++++++++++++++++++++++-------------
>  hw/s390x/s390-pci-bus.h |   1 +
>  2 files changed, 148 insertions(+), 68 deletions(-)
> 

      parent reply	other threads:[~2019-01-16 10:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 10:31 [Qemu-devel] [PATCH v2 0/6] s390x/pci: hotplug handler fixes and reworks David Hildenbrand
2019-01-14 10:31 ` [Qemu-devel] [PATCH v2 1/6] s390x/pci: Use hotplug_dev instead of looking up the host bridge David Hildenbrand
2019-01-15 20:57   ` Collin Walling
2019-01-16  9:22     ` Cornelia Huck
2019-01-14 10:31 ` [Qemu-devel] [PATCH v2 2/6] s390x/pci: Move some hotplug checks to the pre_plug handler David Hildenbrand
2019-01-14 10:31 ` [Qemu-devel] [PATCH v2 3/6] s390x/pci: Always delete and free the release_timer David Hildenbrand
2019-01-15 22:43   ` Collin Walling
2019-01-14 10:31 ` [Qemu-devel] [PATCH v2 4/6] s390x/pci: Ignore the unplug call if we already have a release_timer David Hildenbrand
2019-01-15 22:53   ` Collin Walling
2019-01-16  9:37     ` Cornelia Huck
2019-01-16  9:38     ` David Hildenbrand
2019-01-14 10:31 ` [Qemu-devel] [PATCH v2 5/6] s390x/pci: Introduce unplug requests and split unplug handler David Hildenbrand
2019-01-14 10:31 ` [Qemu-devel] [PATCH v2 6/6] s390x/pci: Unplug remaining devices on pcihost reset David Hildenbrand
2019-01-16 10:19 ` Cornelia Huck [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=20190116111904.6ebd749f.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@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 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.