From: Ira Weiny <ira.weiny@intel.com>
To: Dave Jiang <dave.jiang@intel.com>,
Ira Weiny <ira.weiny@intel.com>, <linux-cxl@vger.kernel.org>
Cc: <dave@stgolabs.net>, <jonathan.cameron@huawei.com>,
<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
<dan.j.williams@intel.com>
Subject: Re: [PATCH 1/2] cxl: Move command enumeration from dev_dbg() to traceevent
Date: Mon, 18 Sep 2023 10:49:28 -0700 [thread overview]
Message-ID: <65088da8ea533_3921be29438@iweiny-mobl.notmuch> (raw)
In-Reply-To: <1b66b8ae-143d-b227-27de-988ee9f0ce04@intel.com>
Dave Jiang wrote:
>
>
> On 9/15/23 15:11, Ira Weiny wrote:
> > Dave Jiang wrote:
> >
[snip]
> > My gut reaction was to nak this patch because I'm not sure how to enable
> > trace events prior to module load. Then I realized that this is in the
> > cxl_core and is only triggered by driver loads. So I've not tested this
> > patch but I think the following sequence will work for these 2 patches.
> >
> > $ modprobe cxl_core
> > $ echo 1 > /sys/kernel/tracing/events/cxl/cxl_log_type/enable
> > $ modprobe cxl_pci
>
> I don't see any other way to do this. I saw this [1] but it doesn't appeared to be upstream.
>
> [1]: https://lwn.net/Articles/432186/
>
> >
> > Is that how you tested this? It seems like a pain. But perhaps that pain
> > is fine because these debug messages are not as useful as others?
> > Especially for all the unsupported messages mentioned in patch 2?
>
> Yes. Alison mentioned seeing maybe 500+ of those.
Ok it seems reasonable to me. But perhaps we can document the above method
somewhere? Not sure if the commit message is the best place but it is better
than nothing.
Thanks,
Ira
next prev parent reply other threads:[~2023-09-18 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 20:13 [PATCH 1/2] cxl: Move command enumeration from dev_dbg() to traceevent Dave Jiang
2023-09-15 20:13 ` [PATCH 2/2] cxl: Move opcode reporting " Dave Jiang
2023-09-18 16:51 ` Alison Schofield
2023-09-18 21:25 ` Ira Weiny
2023-09-15 22:11 ` [PATCH 1/2] cxl: Move command enumeration " Ira Weiny
2023-09-15 22:49 ` Dave Jiang
2023-09-18 17:49 ` Ira Weiny [this message]
2023-09-18 18:21 ` Dave Jiang
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=65088da8ea533_3921be29438@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@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