From: Bart Van Assche <bvanassche@acm.org>
To: Viacheslav Dubeyko <slava@dubeyko.com>, target-devel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org, linux@yadro.com, v.dubeiko@yadro.com,
rostedt@goodmis.org, mingo@redhat.com, r.bolshakov@yadro.com,
k.shelekhin@yadro.com
Subject: Re: [PATCH] scsi: target: core: add task tag to trace events
Date: Thu, 19 Mar 2020 04:29:33 +0000 [thread overview]
Message-ID: <42e02192-4c5a-e19e-a02d-ede3974c18ed@acm.org> (raw)
In-Reply-To: <226e01deaa9baf46d6ff3b8698bc9fe881f7dfc1.camel@dubeyko.com>
On 2020-03-16 06:07, Viacheslav Dubeyko wrote:
> Trace events target_sequencer_start and target_cmd_complete
> (include/trace/events/target.h) are ready to show NAA identifier,
> LUN ID, and many other important command details in the system log:
Reviewed-by: Bart van Assche <bvanassche@acm.org>
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bvanassche@acm.org>
To: Viacheslav Dubeyko <slava@dubeyko.com>, target-devel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org, linux@yadro.com, v.dubeiko@yadro.com,
rostedt@goodmis.org, mingo@redhat.com, r.bolshakov@yadro.com,
k.shelekhin@yadro.com
Subject: Re: [PATCH] scsi: target: core: add task tag to trace events
Date: Wed, 18 Mar 2020 21:29:33 -0700 [thread overview]
Message-ID: <42e02192-4c5a-e19e-a02d-ede3974c18ed@acm.org> (raw)
In-Reply-To: <226e01deaa9baf46d6ff3b8698bc9fe881f7dfc1.camel@dubeyko.com>
On 2020-03-16 06:07, Viacheslav Dubeyko wrote:
> Trace events target_sequencer_start and target_cmd_complete
> (include/trace/events/target.h) are ready to show NAA identifier,
> LUN ID, and many other important command details in the system log:
Reviewed-by: Bart van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2020-03-19 4:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 13:07 [PATCH] scsi: target: core: add task tag to trace events Viacheslav Dubeyko
2020-03-16 13:07 ` Viacheslav Dubeyko
2020-03-19 4:29 ` Bart Van Assche [this message]
2020-03-19 4:29 ` Bart Van Assche
2020-03-27 1:56 ` Martin K. Petersen
2020-03-27 1:56 ` Martin K. Petersen
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=42e02192-4c5a-e19e-a02d-ede3974c18ed@acm.org \
--to=bvanassche@acm.org \
--cc=k.shelekhin@yadro.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=mingo@redhat.com \
--cc=r.bolshakov@yadro.com \
--cc=rostedt@goodmis.org \
--cc=slava@dubeyko.com \
--cc=target-devel@vger.kernel.org \
--cc=v.dubeiko@yadro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.