All of lore.kernel.org
 help / color / mirror / Atom feed
From: Himanshu Madhani <himanshu.madhani@oracle.com>
To: Arun Easi <aeasi@marvell.com>
Cc: Nilesh Javali <njavali@marvell.com>,
	Martin Petersen <martin.petersen@oracle.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"GR-QLogic-Storage-Upstream@marvell.com" 
	<GR-QLogic-Storage-Upstream@marvell.com>,
	"bhazarika@marvell.com" <bhazarika@marvell.com>,
	"agurumurthy@marvell.com" <agurumurthy@marvell.com>
Subject: Re: [PATCH v2 5/7] qla2xxx: Enhance driver tracing with separate tunable and more
Date: Mon, 29 Aug 2022 19:25:34 +0000	[thread overview]
Message-ID: <AFBD250B-7F4D-4C63-B05E-E534F9BC5805@oracle.com> (raw)
In-Reply-To: <ad348f6e-fec6-1ce5-eed5-621f84a5e580@marvell.com>



> On Aug 29, 2022, at 9:59 AM, Arun Easi <aeasi@marvell.com> wrote:
> 
> Thanks for reviewing the code, Himanshu. Response inline..
> 
> On Mon, 29 Aug 2022, 9:24am, Himanshu Madhani wrote:
> 
>> Small nits
>> 
>>> On Aug 26, 2022, at 3:25 AM, Nilesh Javali <njavali@marvell.com> wrote:
>>> 
>>> From: Arun Easi <aeasi@marvell.com>
>>> 
>>> Older tracing of driver messages was to:
>>>   - log only debug messages to kernel main trace buffer AND
>>>   - log only if extended logging bits corresponding to this
>>>     message is off
>>> 
>>> This has been modified and extended as follows:
>>>   - Tracing is now controlled via ql2xextended_error_logging_ktrace
>>>     module parameter. Bit usages same as ql2xextended_error_logging.
>>>   - Tracing uses "qla2xxx" trace instance, unless instance creation
>>>     have issues.
>>>   - Tracing is enabled (compile time tunable).
>>>   - All driver messages, include debug and log messages are now traced
>>>     in kernel trace buffer.
>>> 
>>> Trace messages can be viewed by looking at the qla2xxx instance at:
>>>   /sys/kernel/tracing/instances/qla2xxx/trace
>>> 
>> ^^^^^^^^
>> This should be /sys/kernel/debug/tracing/instances/qla2xxx/trace
>> 
> 
> With tracefs, the location is moved to:
> 	/sys/kernel/tracing
> 
> ..with old location preserved.
> 

Okay got it... I think I got tripped by the nuance of tracefs to be mounted to see a new tracing directory to be populated.

Here’s what I had seen on my 6.0.0-rc1+ kernel,

I could not locate it at /sys/kernel/tracing instead old location which makes sense from the Documentation

root@tatoonie~6.0.0-rc1+:/# ls -l /sys/kernel/tracing/
total 0
root@tatoonie~6.0.0-rc1+:/# ls -l /sys/kernel/debug/tracing/instances/qla2xxx/trace
-rw-r----- 1 root root 0 Aug 29 08:54 /sys/kernel/debug/tracing/instances/qla2xxx/trace

maybe you can add a comment indicating tracefs should be mounted to see traces at 
/sys/kernel/tracing.

FYI.. you can also add 

Tested-by: Himanshu Madhani <himanshu.madhani@oracle.com>


> Regards,
> -Arun
> PS: # grep -A 10 '^The File System' Documentation/trace/ftrace.rst

-- 
Himanshu Madhani	Oracle Linux Engineering


  reply	other threads:[~2022-08-29 19:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 10:25 [PATCH v2 0/7] qla2xxx driver features Nilesh Javali
2022-08-26 10:25 ` [PATCH v2 1/7] Revert "scsi: qla2xxx: Fix response queue handler reading stale packets" Nilesh Javali
2022-08-29 16:09   ` Himanshu Madhani
2022-08-26 10:25 ` [PATCH v2 2/7] qla2xxx: Fix response queue handler reading stale packets Nilesh Javali
2022-08-29 16:10   ` Himanshu Madhani
2022-08-26 10:25 ` [PATCH v2 3/7] qla2xxx: Add debugfs create/delete helpers Nilesh Javali
2022-08-29 16:10   ` Himanshu Madhani
2022-08-26 10:25 ` [PATCH v2 4/7] qla2xxx: Add NVMe parameters support in Auxiliary Image Status Nilesh Javali
2022-08-29 16:15   ` Himanshu Madhani
2022-08-26 10:25 ` [PATCH v2 5/7] qla2xxx: Enhance driver tracing with separate tunable and more Nilesh Javali
2022-08-29 16:24   ` Himanshu Madhani
2022-08-29 16:59     ` Arun Easi
2022-08-29 19:25       ` Himanshu Madhani [this message]
2022-08-30  7:55         ` Daniel Wagner
2022-09-01 13:41           ` Steven Rostedt
2022-08-30  8:07   ` Daniel Wagner
2022-09-19 22:01   ` Guenter Roeck
2022-09-19 23:15     ` Arun Easi
2022-08-26 10:25 ` [PATCH v2 6/7] qla2xxx: define static symbols Nilesh Javali
2022-08-29 16:25   ` Himanshu Madhani
2022-08-26 10:25 ` [PATCH v2 7/7] qla2xxx: Update version to 10.02.07.900-k Nilesh Javali
2022-08-29 16:26   ` Himanshu Madhani
2022-09-01  4:31 ` [PATCH v2 0/7] qla2xxx driver features 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=AFBD250B-7F4D-4C63-B05E-E534F9BC5805@oracle.com \
    --to=himanshu.madhani@oracle.com \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=aeasi@marvell.com \
    --cc=agurumurthy@marvell.com \
    --cc=bhazarika@marvell.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=njavali@marvell.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.