From: Cornelia Huck <cohuck@redhat.com>
To: Eric Farman <farman@linux.ibm.com>
Cc: Steffen Maier <maier@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
Jared Rossi <jrossi@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v2 3/4] vfio-ccw: Add a trace for asynchronous requests
Date: Wed, 16 Oct 2019 13:39:19 +0200 [thread overview]
Message-ID: <20191016133919.6f8592e7.cohuck@redhat.com> (raw)
In-Reply-To: <6c559ea3-4abd-d83b-4a20-d022a188545e@linux.ibm.com>
On Wed, 16 Oct 2019 07:36:09 -0400
Eric Farman <farman@linux.ibm.com> wrote:
> On 10/16/19 6:15 AM, Cornelia Huck wrote:
> > On Wed, 16 Oct 2019 03:58:21 +0200
> > Eric Farman <farman@linux.ibm.com> wrote:
> >
> >> Since the asynchronous requests are typically associated with
> >> error recovery, let's add a simple trace when one of those is
> >> issued to a device.
> >>
> >> Signed-off-by: Eric Farman <farman@linux.ibm.com>
> >> ---
> >> drivers/s390/cio/vfio_ccw_fsm.c | 4 ++++
> >> drivers/s390/cio/vfio_ccw_trace.c | 1 +
> >> drivers/s390/cio/vfio_ccw_trace.h | 30 ++++++++++++++++++++++++++++++
> >> 3 files changed, 35 insertions(+)
> >
> > (...)
> >
> >> diff --git a/drivers/s390/cio/vfio_ccw_trace.h b/drivers/s390/cio/vfio_ccw_trace.h
> >> index 5005d57901b4..23b288eb53dc 100644
> >> --- a/drivers/s390/cio/vfio_ccw_trace.h
> >> +++ b/drivers/s390/cio/vfio_ccw_trace.h
> >> @@ -17,6 +17,36 @@
> >>
> >> #include <linux/tracepoint.h>
> >>
> >> +TRACE_EVENT(vfio_ccw_fsm_async_request,
> >> + TP_PROTO(struct subchannel_id schid,
> >> + int command,
> >> + int errno),
> >> + TP_ARGS(schid, command, errno),
> >> +
> >> + TP_STRUCT__entry(
> >> + __field(u8, cssid)
> >> + __field(u8, ssid)
> >> + __field(u16, sch_no)
> >> + __field(int, command)
> >> + __field(int, errno)
> >> + ),
> >> +
> >> + TP_fast_assign(
> >> + __entry->cssid = schid.cssid;
> >> + __entry->ssid = schid.ssid;
> >> + __entry->sch_no = schid.sch_no;
> >> + __entry->command = command;
> >> + __entry->errno = errno;
> >> + ),
> >> +
> >> + TP_printk("schid=%x.%x.%04x command=%d errno=%d",
> >
> > I'd probably rather print the command as a hex value.
>
> I'm fine with that too. Want me to send an update?
I think that would be the easiest way.
>
> >
> >> + __entry->cssid,
> >> + __entry->ssid,
> >> + __entry->sch_no,
> >> + __entry->command,
> >> + __entry->errno)
> >> +);
> >> +
> >> TRACE_EVENT(vfio_ccw_fsm_event,
> >> TP_PROTO(struct subchannel_id schid, int state, int event),
> >> TP_ARGS(schid, state, event),
> >
next prev parent reply other threads:[~2019-10-16 11:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 1:58 [PATCH v2 0/4] vfio-ccw: A couple trace changes Eric Farman
2019-10-16 1:58 ` [PATCH v2 1/4] vfio-ccw: Refactor how the traces are built Eric Farman
2019-10-16 10:08 ` Cornelia Huck
2019-10-16 1:58 ` [PATCH v2 2/4] vfio-ccw: Trace the FSM jumptable Eric Farman
2019-10-16 10:10 ` Cornelia Huck
2019-10-16 1:58 ` [PATCH v2 3/4] vfio-ccw: Add a trace for asynchronous requests Eric Farman
2019-10-16 10:15 ` Cornelia Huck
2019-10-16 11:36 ` Eric Farman
2019-10-16 11:39 ` Cornelia Huck [this message]
2019-10-16 13:35 ` Eric Farman
2019-10-16 1:58 ` [PATCH v2 4/4] vfio-ccw: Rework the io_fctl trace Eric Farman
2019-10-16 10:17 ` 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=20191016133919.6f8592e7.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=maier@linux.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox