public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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 0/4] vfio-ccw: A couple trace changes
Date: Thu, 17 Oct 2019 12:19:24 +0200	[thread overview]
Message-ID: <20191017121924.3597aa7f.cohuck@redhat.com> (raw)
In-Reply-To: <20191016142040.14132-1-farman@linux.ibm.com>

On Wed, 16 Oct 2019 16:20:36 +0200
Eric Farman <farman@linux.ibm.com> wrote:

> Here a couple updates to the vfio-ccw traces in the kernel,
> based on things I've been using locally.  Perhaps they'll
> be useful for future debugging.
> 
> v2 -> v3:
>  - Added Conny's r-b to patches 1, 2, 4
>  - s/command=%d/command=0x%x/ in patch 3 [Cornelia Huck]
> 
> v1/RFC -> v2:
>  - Convert state/event=%x to %d [Steffen Maier]
>  - Use individual fields for cssid/ssid/sch_no, to enable
>    filtering by device [Steffen Maier]
>  - Add 0x prefix to remaining %x substitution in existing trace
> 
> Eric Farman (4):
>   vfio-ccw: Refactor how the traces are built
>   vfio-ccw: Trace the FSM jumptable
>   vfio-ccw: Add a trace for asynchronous requests
>   vfio-ccw: Rework the io_fctl trace
> 
>  drivers/s390/cio/Makefile           |  4 +-
>  drivers/s390/cio/vfio_ccw_cp.h      |  1 +
>  drivers/s390/cio/vfio_ccw_fsm.c     | 11 +++--
>  drivers/s390/cio/vfio_ccw_private.h |  1 +
>  drivers/s390/cio/vfio_ccw_trace.c   | 14 ++++++
>  drivers/s390/cio/vfio_ccw_trace.h   | 76 ++++++++++++++++++++++++++---
>  6 files changed, 93 insertions(+), 14 deletions(-)
>  create mode 100644 drivers/s390/cio/vfio_ccw_trace.c
> 

Thanks, applied.

      parent reply	other threads:[~2019-10-17 10:19 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
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 [this message]

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=20191017121924.3597aa7f.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