From: Pierre Morel <pmorel@linux.ibm.com>
To: pasic@linux.vnet.ibm.com
Cc: cohuck@redhat.com, farman@linux.ibm.com, alifm@linux.ibm.com,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: [PATCH v3 0/6] vfio: ccw: VFIO CCW cleanup part1
Date: Wed, 28 Nov 2018 13:41:01 +0100 [thread overview]
Message-ID: <1543408867-16465-1-git-send-email-pmorel@linux.ibm.com> (raw)
The goal of the patches of this serie is to clarify the code
of state/event handling.
- First patch (already acked/applied) makes sure that every structures are initialized
before the mediated device is registered.
(Only here to apply the serie on the main tree).
- vfio: ccw: Rework subchannel state on setup
makes sure that the device can not be used before a guest is
ready to drive it.
- vfio: ccw: Rework subchannel state on removing
could be squash with the previous: same kind of rewriting
but for the removing/release callbacks.
- vfio: ccw: Rework subchannel state on sch_event
sch_event handling seems quite poor to me.
Anyway, I do not understand why we hould have state change there.
- vfio: ccw: Documenting state transitions
- vfio: ccw: serialize the write system calls
Quite independent of the previous patches, this makes sure
that the entry in the driver is serialized.
Pierre Morel (6):
vfio: ccw: Register mediated device once all structures are
initialized
vfio: ccw: Rework subchannel state on setup
vfio: ccw: Rework subchannel state on removing
vfio: ccw: Rework subchannel state on sch_event
vfio: ccw: Documenting state transitions
vfio: ccw: serialize the write system calls
Documentation/s390/vfio-ccw.txt | 45 +++++++++++++++++++++++++
drivers/s390/cio/vfio_ccw_async.c | 11 +++++++
drivers/s390/cio/vfio_ccw_drv.c | 30 ++++-------------
drivers/s390/cio/vfio_ccw_ops.c | 65 ++++++++++++++++++++++++-------------
drivers/s390/cio/vfio_ccw_private.h | 1 +
5 files changed, 105 insertions(+), 47 deletions(-)
--
2.7.4
Changelog:
from v2:
- adaptation after Conny's hlt/clr patches
- integration of Conny's comments
- reworking of the state changes to make it clearer
- added documentation
- added serialization
from v1:
- change commit message
- add reviewed-by from Eric (Really this time)
from v0:
- isolate these two patches from the previous serie
- Added Reviewed-by Eric
- Ortographic correction
next reply other threads:[~2018-11-28 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 12:41 Pierre Morel [this message]
2018-11-28 12:41 ` [PATCH v3 1/6] vfio: ccw: Register mediated device once all structures are initialized Pierre Morel
2018-11-28 12:41 ` [PATCH v3 2/6] vfio: ccw: Rework subchannel state on setup Pierre Morel
2018-12-18 17:44 ` Eric Farman
2018-12-19 9:51 ` Pierre Morel
2018-11-28 12:41 ` [PATCH v3 3/6] vfio: ccw: Rework subchannel state on removing Pierre Morel
2018-11-28 12:41 ` [PATCH v3 4/6] vfio: ccw: Rework subchannel state on sch_event Pierre Morel
2018-11-28 12:41 ` [PATCH v3 5/6] vfio: ccw: Documenting state transitions Pierre Morel
2018-11-28 12:41 ` [PATCH v3 6/6] vfio: ccw: serialize the write system calls Pierre Morel
2018-12-13 15:39 ` Cornelia Huck
2018-12-14 12:42 ` Halil Pasic
2018-12-14 14:08 ` Pierre Morel
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=1543408867-16465-1-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.vnet.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).