From: Cornelia Huck <cohuck@redhat.com>
To: Eric Farman <farman@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org,
Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
Jared Rossi <jrossi@linux.ibm.com>
Subject: Re: [PATCH v4 7/8] vfio-ccw: Wire up the CRW irq and CRW region
Date: Wed, 6 May 2020 15:52:59 +0200 [thread overview]
Message-ID: <20200506155259.4ec538e2.cohuck@redhat.com> (raw)
In-Reply-To: <20200505122745.53208-8-farman@linux.ibm.com>
On Tue, 5 May 2020 14:27:44 +0200
Eric Farman <farman@linux.ibm.com> wrote:
> From: Farhan Ali <alifm@linux.ibm.com>
>
> Use the IRQ to notify userspace that there is a CRW
> pending in the region, related to path-availability
> changes on the passthrough subchannel.
>
> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
> Signed-off-by: Eric Farman <farman@linux.ibm.com>
> ---
>
> Notes:
> v3->v4:
> - s/vfio_ccw_alloc_crw()/vfio_ccw_queue_crw()/ [CH]
> - Remove cssid from crw that is built [CH]
>
> v2->v3:
> - Refactor vfio_ccw_alloc_crw() to accept rsc, erc, and rsid fields
> of a CRW as input [CH]
> - Copy the right amount of CRWs to the crw_region [EF]
> - Use sizeof(target) for the memcpy, rather than sizeof(source) [EF]
> - Ensure the CRW region is empty if no CRW is present [EF/CH]
> - Refactor how data goes from private-to-region-to-user [CH]
> - Reduce the number of CRWs from two to one [CH]
> - s/vc_crw/crw/ [EF]
>
> v1->v2:
> - Remove extraneous 0x0 in crw.rsid assignment [CH]
> - Refactor the building/queueing of a crw into its own routine [EF]
>
> v0->v1: [EF]
> - Place the non-refactoring changes from the previous patch here
> - Clean up checkpatch (whitespace) errors
> - s/chp_crw/crw/
> - Move acquire/release of io_mutex in vfio_ccw_crw_region_read()
> into patch that introduces that region
> - Remove duplicate include from vfio_ccw_drv.c
> - Reorder include in vfio_ccw_private.h
>
> drivers/s390/cio/vfio_ccw_chp.c | 17 ++++++++++
> drivers/s390/cio/vfio_ccw_drv.c | 49 +++++++++++++++++++++++++++++
> drivers/s390/cio/vfio_ccw_private.h | 8 +++++
> 3 files changed, 74 insertions(+)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2020-05-06 13:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 12:27 [PATCH v4 0/8] s390x/vfio-ccw: Channel Path Handling [KVM] Eric Farman
2020-05-05 12:27 ` [PATCH v4 1/8] vfio-ccw: Introduce new helper functions to free/destroy regions Eric Farman
2020-05-05 12:27 ` [PATCH v4 2/8] vfio-ccw: Register a chp_event callback for vfio-ccw Eric Farman
2020-05-06 13:18 ` Cornelia Huck
2020-05-05 12:27 ` [PATCH v4 3/8] vfio-ccw: Refactor the unregister of the async regions Eric Farman
2020-05-05 12:27 ` [PATCH v4 4/8] vfio-ccw: Introduce a new schib region Eric Farman
2020-05-05 12:27 ` [PATCH v4 5/8] vfio-ccw: Refactor IRQ handlers Eric Farman
2020-05-05 12:27 ` [PATCH v4 6/8] vfio-ccw: Introduce a new CRW region Eric Farman
2020-05-06 13:24 ` Cornelia Huck
2020-05-05 12:27 ` [PATCH v4 7/8] vfio-ccw: Wire up the CRW irq and " Eric Farman
2020-05-06 13:52 ` Cornelia Huck [this message]
2020-05-05 12:27 ` [PATCH v4 8/8] vfio-ccw: Add trace for CRW event Eric Farman
2020-05-05 12:56 ` [PATCH v4 0/8] s390x/vfio-ccw: Channel Path Handling [KVM] Cornelia Huck
2020-05-05 13:00 ` Eric Farman
2020-05-06 13:59 ` Cornelia Huck
2020-05-18 10:05 ` Cornelia Huck
2020-05-18 10:14 ` Eric Farman
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=20200506155259.4ec538e2.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=jrossi@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@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.