[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180410105540.310ea82a.cohuck@redhat.com>
Date: Tue, 10 Apr 2018 10:55:40 +0200
From: Cornelia Huck <cohuck@...hat.com>
To: Dong Jia Shi <bjsdjshi@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
kvm@...r.kernel.org, borntraeger@...ibm.com,
pasic@...ux.vnet.ibm.com, pmorel@...ux.vnet.ibm.com
Subject: Re: [PATCH 4/4] vfio: ccw: add traceponits for interesting error
paths
On Tue, 10 Apr 2018 10:16:39 +0800
Dong Jia Shi <bjsdjshi@...ux.vnet.ibm.com> wrote:
> Does the following effect make sense?
>
> # tracer: nop
> #
> # _-----=> irqs-off
> # / _----=> need-resched
> # | / _---=> hardirq/softirq
> # || / _--=> preempt-depth
> # ||| / delay
> # TASK-PID CPU# |||| TIMESTAMP FUNCTION
> # | | | |||| | |
> qemu-system-s39-4252 [006] .... 231.457214: vfio_ccw_cp_prefetch: schid=0.0.013f errno=0
> qemu-system-s39-4252 [006] .... 231.457222: vfio_ccw_fsm_io_helper: schid=0.0.013f errno=0
> qemu-system-s39-4252 [006] .... 231.457223: vfio_ccw_io_fctl: schid=0.0.013f fctl=4 errno=0
> ... ...
I would likely find this useful for following a code path and making
sure the right things are called.
We certainly want error conditions traced as well (although the code
has been working too well for me to trigger that easily :)
Powered by blists - more mailing lists