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 3/3] vfio-ccw: Release any channel program when releasing/removing vfio-ccw mdev
Date: Fri, 12 Apr 2019 10:12:36 +0200 [thread overview]
Message-ID: <20190412101236.4f753e6d.cohuck@redhat.com> (raw)
In-Reply-To: <7123f8b7-0348-4140-1b94-5d35ea1ef567@linux.ibm.com>
On Thu, 11 Apr 2019 16:39:32 -0400
Farhan Ali <alifm@linux.ibm.com> wrote:
> On 04/11/2019 12:27 PM, Cornelia Huck wrote:
> > On Mon, 8 Apr 2019 17:05:33 -0400
> > Farhan Ali<alifm@linux.ibm.com> wrote:
> >
> >> When releasing the vfio-ccw mdev, we currently do not release
> >> any existing channel program and it's pinned pages. This can
> > s/it's/its/
> >
>
> Will fix.
>
> Thanks for taking a look at the patches.
NP, I really want to queue them soon :)
Just give me a quick hint about dependencies: Do I need anything else
before I can queue patch 1 and 3? I've lost track a bit...
next prev parent reply other threads:[~2019-04-12 8:12 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
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 [this message]
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=20190412101236.4f753e6d.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox