From: "Gilad Broner" <gbroner@codeaurora.org>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: "Gilad Broner" <gbroner@codeaurora.org>,
james.bottomley@hansenpartnership.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-arm-msm@vger.kernel.org, santoshsy@gmail.com,
linux-scsi-owner@vger.kernel.org, subhashj@codeaurora.org,
ygardi@codeaurora.org, draviv@codeaurora.org,
"Lee Susman" <lsusman@codeaurora.org>,
"Sujit Reddy Thumma" <sthumma@codeaurora.org>,
"Vinayak Holikatti" <vinholikatti@gmail.com>,
"James E.J. Bottomley" <jbottomley@parallels.com>,
"Ingo Molnar" <mingo@redhat.com>
Subject: Re: [PATCH v2 3/4] scsi: ufs: add trace events and dump prints for debug
Date: Sun, 22 Feb 2015 14:58:34 -0000 [thread overview]
Message-ID: <c7bcf021bd1c2cfe9ca02669bf11f5f5.squirrel@codeaurora.org> (raw)
In-Reply-To: <20150212145551.2d234fb1@gandalf.local.home>
>> struct ufs_stats {
>> +#ifdef CONFIG_DEBUG_FS
>> bool enabled;
>> u64 **tag_stats;
>> int q_depth;
>> int err_stats[UFS_ERR_MAX];
>> +#endif
>
> Can any of the tracepoint code be called that references these when
> CONFIG_DEBUG_FS is not set? Because soon (possibly even this merge
> window), tracing will no longer depend on DEBUG_FS, because it will
> have its own filesystem.
Thanks for the update about this dependency.
None of these are used for the tracepoints, so I don't expect any problems.
Gilad.
--
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-02-22 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 13:58 [PATCH v2 0/4] Add ioctl and debug utilities to UFS driver Gilad Broner
2015-02-10 13:58 ` [PATCH v2 1/4] scsi: ufs: add ioctl interface for query request Gilad Broner
2015-02-10 13:58 ` [PATCH v2 2/4] scsi: ufs: add debugfs for ufs Gilad Broner
2015-02-12 13:53 ` Akinobu Mita
2015-02-22 15:00 ` Gilad Broner
2015-02-10 13:58 ` [PATCH v2 3/4] scsi: ufs: add trace events and dump prints for debug Gilad Broner
2015-02-12 19:55 ` Steven Rostedt
2015-02-22 14:58 ` Gilad Broner [this message]
2015-02-10 13:58 ` [PATCH v2 4/4] scsi: ufs: inject errors to verify error handling Gilad Broner
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=c7bcf021bd1c2cfe9ca02669bf11f5f5.squirrel@codeaurora.org \
--to=gbroner@codeaurora.org \
--cc=draviv@codeaurora.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=jbottomley@parallels.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsusman@codeaurora.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=santoshsy@gmail.com \
--cc=sthumma@codeaurora.org \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=ygardi@codeaurora.org \
/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