From: Cornelia Huck <cohuck@redhat.com>
To: Dong Jia Shi <bjsdjshi@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, borntraeger@de.ibm.com, pasic@linux.ibm.com,
pmorel@linux.ibm.com
Subject: Re: [PATCH v4 4/4] vfio: ccw: add traceponits for interesting error paths
Date: Wed, 23 May 2018 12:25:55 +0200 [thread overview]
Message-ID: <20180523122555.75c262a7.cohuck@redhat.com> (raw)
In-Reply-To: <20180523025645.8978-5-bjsdjshi@linux.ibm.com>
On Wed, 23 May 2018 04:56:45 +0200
Dong Jia Shi <bjsdjshi@linux.ibm.com> wrote:
Still s/traceponits/tracepoints/ (can fix up when applying).
> From: Halil Pasic <pasic@linux.ibm.com>
>
> Add some tracepoints so we can inspect what is not working as is should.
>
> Signed-off-by: Halil Pasic <pasic@linux.ibm.com>
> Signed-off-by: Dong Jia Shi <bjsdjshi@linux.ibm.com>
> ---
> drivers/s390/cio/Makefile | 1 +
> drivers/s390/cio/vfio_ccw_fsm.c | 17 +++++++++++-
> drivers/s390/cio/vfio_ccw_trace.h | 54 +++++++++++++++++++++++++++++++++++++++
> 3 files changed, 71 insertions(+), 1 deletion(-)
> create mode 100644 drivers/s390/cio/vfio_ccw_trace.h
>
> diff --git a/drivers/s390/cio/Makefile b/drivers/s390/cio/Makefile
> index a070ef0efe65..f230516abb96 100644
> --- a/drivers/s390/cio/Makefile
> +++ b/drivers/s390/cio/Makefile
> @@ -5,6 +5,7 @@
>
> # The following is required for define_trace.h to find ./trace.h
> CFLAGS_trace.o := -I$(src)
> +CFLAGS_vfio_ccw_fsm.o := -I$(src)
>
> obj-y += airq.o blacklist.o chsc.o cio.o css.o chp.o idset.o isc.o \
> fcx.o itcw.o crw.o ccwreq.o trace.o ioasm.o
> diff --git a/drivers/s390/cio/vfio_ccw_fsm.c b/drivers/s390/cio/vfio_ccw_fsm.c
> index 3c800642134e..797a82731159 100644
> --- a/drivers/s390/cio/vfio_ccw_fsm.c
> +++ b/drivers/s390/cio/vfio_ccw_fsm.c
> @@ -13,6 +13,9 @@
> #include "ioasm.h"
> #include "vfio_ccw_private.h"
>
> +#define CREATE_TRACE_POINTS
> +#include "vfio_ccw_trace.h"
> +
> static int fsm_io_helper(struct vfio_ccw_private *private)
> {
> struct subchannel *sch;
> @@ -110,6 +113,10 @@ static void fsm_disabled_irq(struct vfio_ccw_private *private,
> */
> cio_disable_subchannel(sch);
> }
> +inline struct subchannel_id get_schid(struct vfio_ccw_private *p)
> +{
> + return p->sch->schid;
> +}
>
> /*
> * Deal with the ccw command request from the userspace.
> @@ -121,6 +128,7 @@ static void fsm_io_request(struct vfio_ccw_private *private,
> union scsw *scsw = &private->scsw;
> struct ccw_io_region *io_region = &private->io_region;
> struct mdev_device *mdev = private->mdev;
> + char *errstr = "request";
>
> private->state = VFIO_CCW_STATE_BOXED;
>
> @@ -132,15 +140,19 @@ static void fsm_io_request(struct vfio_ccw_private *private,
> /* Don't try to build a cp if transport mode is specified. */
> if (orb->tm.b) {
> io_region->ret_code = -EOPNOTSUPP;
> + errstr = "transport mode";
> goto err_out;
> }
> io_region->ret_code = cp_init(&private->cp, mdev_dev(mdev),
> orb);
> - if (io_region->ret_code)
> + if (io_region->ret_code) {
> + errstr = "cp init";
> goto err_out;
> + }
>
> io_region->ret_code = cp_prefetch(&private->cp);
> if (io_region->ret_code) {
> + errstr = "cp prefetch";
> cp_free(&private->cp);
> goto err_out;
> }
> @@ -148,6 +160,7 @@ static void fsm_io_request(struct vfio_ccw_private *private,
> /* Start channel program and wait for I/O interrupt. */
> io_region->ret_code = fsm_io_helper(private);
> if (io_region->ret_code) {
> + errstr = "cp fsm_io_helper";
> cp_free(&private->cp);
> goto err_out;
> }
> @@ -164,6 +177,8 @@ static void fsm_io_request(struct vfio_ccw_private *private,
>
> err_out:
> private->state = VFIO_CCW_STATE_IDLE;
> + trace_vfio_ccw_io_fctl(scsw->cmd.fctl, get_schid(private),
> + io_region->ret_code, errstr);
> }
>
> /*
This approach looks reasonable to me. We can still improve this later,
should we want to.
next prev parent reply other threads:[~2018-05-23 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 2:56 [PATCH v4 0/4] vfio: ccw: error handling fixes and improvements Dong Jia Shi
2018-05-23 2:56 ` [PATCH v4 1/4] vfio: ccw: shorten kernel doc description for pfn_array_pin() Dong Jia Shi
2018-05-23 2:56 ` [PATCH v4 2/4] vfio: ccw: refactor and improve pfn_array_alloc_pin() Dong Jia Shi
2018-05-23 2:56 ` [PATCH v4 3/4] vfio: ccw: set ccw->cda to NULL defensively Dong Jia Shi
2018-05-23 2:56 ` [PATCH v4 4/4] vfio: ccw: add traceponits for interesting error paths Dong Jia Shi
2018-05-23 10:25 ` Cornelia Huck [this message]
2018-05-23 10:21 ` [PATCH v4 0/4] vfio: ccw: error handling fixes and improvements Cornelia Huck
2018-05-24 14:29 ` 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=20180523122555.75c262a7.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=bjsdjshi@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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