From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org,
Lakshminarayana Vudum <lakshminarayana.vudum@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 2/3] lib: Add more debugfs and ftrace helpers
Date: Wed, 10 Apr 2019 21:41:33 -0700 [thread overview]
Message-ID: <87v9zlgnlu.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <155479806393.26510.7380624782685919820@skylake-alporthouse-com>
On Tue, 09 Apr 2019 01:21:03 -0700, Chris Wilson wrote:
>
> Quoting Ashutosh Dixit (2019-04-02 03:44:20)
> > +/* Implement 'echo 0/1 > <debugfs>/tracing/str[i]' */
> > +int igt_ftrace_set_events(const char **str, int nstr, bool enable)
> > +{
> > + int i, ret, err = 0;
> > +
> > + if (igt_ftrace.dir < 0)
> > + return -ENODEV;
> > +
> > + for (i = 0; i < nstr; i++) {
> > + ret = igt_sysfs_set(igt_ftrace.dir, str[i],
> > + enable ? "1\n" : "0\n");
> > + if (ret)
> > + err = ret;
> > + }
>
> Why didn't you extend the set of options passed to enable?
Hi Chris, which particular options are you referring to? (This function is
enabling ftrace events according to the method in Section 2.2,
Documentation/trace/events.rst. Please see Patch 3/3 for how this function
is used). Some options are enabled in __igt_ftrace_enable() in Patch 1/3
(your patch).
> Do we want to be adjusting these as the test runs, or should it be setup
> once for the test?
Again please see Patch 3/3, the options are set up in igt_fixture once for
the test. Thanks.
--
Ashutosh
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-11 4:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 2:44 [igt-dev] [PATCH i-g-t 1/3] lib: Add hooks for enabling ftrace Ashutosh Dixit
2019-04-02 2:44 ` [igt-dev] [PATCH i-g-t 2/3] lib: Add more debugfs and ftrace helpers Ashutosh Dixit
2019-04-09 8:21 ` Chris Wilson
2019-04-11 4:41 ` Ashutosh Dixit [this message]
2019-04-02 2:44 ` [igt-dev] [PATCH i-g-t 3/3] lib: Enable extra kernel logs for audio debug Ashutosh Dixit
2019-04-02 6:39 ` Jani Nikula
2019-04-09 2:40 ` Ashutosh Dixit
2019-04-02 8:57 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/3] lib: Add hooks for enabling ftrace Patchwork
2019-04-02 13:04 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-04-03 0:45 [igt-dev] [PATCH i-g-t 1/3] " Ashutosh Dixit
2019-04-03 0:45 ` [igt-dev] [PATCH i-g-t 2/3] lib: Add more debugfs and ftrace helpers Ashutosh Dixit
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=87v9zlgnlu.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=lakshminarayana.vudum@intel.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