From: Cornelia Huck <cohuck@redhat.com>
To: Eric Farman <farman@linux.ibm.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
Steffen Maier <maier@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 v3 3/4] vfio-ccw: Add a trace for asynchronous requests
Date: Thu, 17 Oct 2019 11:35:29 +0200 [thread overview]
Message-ID: <20191017113529.338bad06.cohuck@redhat.com> (raw)
In-Reply-To: <20191016142040.14132-4-farman@linux.ibm.com>
On Wed, 16 Oct 2019 16:20:39 +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(+)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2019-10-17 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 14:20 [PATCH v3 0/4] vfio-ccw: A couple trace changes Eric Farman
2019-10-16 14:20 ` [PATCH v3 1/4] vfio-ccw: Refactor how the traces are built Eric Farman
2019-10-16 14:20 ` [PATCH v3 2/4] vfio-ccw: Trace the FSM jumptable Eric Farman
2019-10-16 14:20 ` [PATCH v3 3/4] vfio-ccw: Add a trace for asynchronous requests Eric Farman
2019-10-17 9:35 ` Cornelia Huck [this message]
2019-10-16 14:20 ` [PATCH v3 4/4] vfio-ccw: Rework the io_fctl trace Eric Farman
2019-10-16 14:30 ` [PATCH v3 0/4] vfio-ccw: A couple trace changes Halil Pasic
2019-10-17 10:19 ` 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=20191017113529.338bad06.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