From: Cornelia Huck <cohuck@redhat.com>
To: Farhan Ali <alifm@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
farman@linux.ibm.com, pasic@linux.ibm.com, pmorel@linux.ibm.com
Subject: Re: [RFC v2 2/3] vfio-ccw: Prevent quiesce function going into an infinite loop
Date: Mon, 15 Apr 2019 16:44:43 +0200 [thread overview]
Message-ID: <20190415164443.4a418f97.cohuck@redhat.com> (raw)
In-Reply-To: <7f1f3844-9108-fea8-a723-1d1d5c0047cd@linux.ibm.com>
On Mon, 15 Apr 2019 10:24:53 -0400
Farhan Ali <alifm@linux.ibm.com> wrote:
> On 04/15/2019 10:18 AM, Cornelia Huck wrote:
> > Yes, please do send it separately. I'm currently testing patch 1 and 3
> > on top of my patchset, will queue either with or without the halt/clear
> > patches proper, depending on how soon I get acks/r-bs (hint, hint :)
>
> I am going through your patches 4 and 6 and hopefully will get back to
> you by the end of the day :).
Awesome, thanks!
next prev parent reply other threads:[~2019-04-15 14:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 21:05 [RFC v2 0/3] fio-ccw fixes for kernel stacktraces Farhan Ali
2019-04-08 21:05 ` [RFC v2 1/3] vfio-ccw: Do not call flush_workqueue while holding the spinlock Farhan Ali
2019-04-08 21:05 ` [RFC v2 2/3] vfio-ccw: Prevent quiesce function going into an infinite loop Farhan Ali
2019-04-11 16:24 ` Cornelia Huck
2019-04-11 20:30 ` Farhan Ali
2019-04-12 8:10 ` Cornelia Huck
2019-04-12 14:38 ` Farhan Ali
2019-04-15 8:13 ` Cornelia Huck
2019-04-15 13:38 ` Farhan Ali
2019-04-15 14:18 ` Cornelia Huck
2019-04-15 14:24 ` Farhan Ali
2019-04-15 14:44 ` Cornelia Huck [this message]
2019-04-08 21:05 ` [RFC v2 3/3] vfio-ccw: Release any channel program when releasing/removing vfio-ccw mdev Farhan Ali
2019-04-11 16:27 ` Cornelia Huck
2019-04-11 20:39 ` Farhan Ali
2019-04-12 8:12 ` Cornelia Huck
2019-04-12 14:13 ` Farhan Ali
2019-04-12 21:03 ` Eric Farman
2019-04-12 21:01 ` Eric Farman
2019-04-15 16:45 ` [RFC v2 0/3] fio-ccw fixes for kernel stacktraces Cornelia Huck
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=20190415164443.4a418f97.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=pmorel@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.