From: Alison Schofield <alison.schofield@intel.com>
To: Marek Bykowski <marek.bykowski@gmail.com>
Cc: linux-cxl@vger.kernel.org
Subject: Re: trace events
Date: Thu, 17 Nov 2022 16:50:56 -0800 [thread overview]
Message-ID: <Y3bW8CLw8xcbrfav@aschofie-mobl2> (raw)
In-Reply-To: <20221114202242.5f9023d3@ubuntu.armcompdev.pub.tds.tieto.com>
On Mon, Nov 14, 2022 at 08:27:57PM +0000, Marek Bykowski wrote:
> Hello cxl mailing list,
>
> I just started a project for validating the RTL of the CXL root bridge
> from Intel. One of my first goals is to better understand the
> SW/protocol flows, so that we better validate it. I'm going to use
> the tracpoints for it and possibly lttng. Are you considering adding
> some of it shortly? If not would you be interested into the patches for
> it?
>
> On the list I'm seeing include/trace/events/cxl.h but on the repository
> kernel/git/cxl/cxl.git seeing none for example with:
>
> git cat-file -e origin:include/trace/events/cxl.h
Hi Marek,
There are a few patchsets under review that are using trace events
in CXL. I'm working on one for CXL Poison Retrieval.
There is also tool support, the monitor patchset, making its way
upstream for ndctl that uses the trace events.
I haven't looked at lttng.
Can you share more about your project?
Thanks,
Alison
>
> Thanks,
> Marek
next prev parent reply other threads:[~2022-11-18 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 20:27 trace events Marek Bykowski
2022-11-18 0:50 ` Alison Schofield [this message]
2022-11-18 13:53 ` Marek Bykowski
2022-11-18 15:18 ` Dave Jiang
2022-11-18 22:39 ` Marek Bykowski
2022-11-18 23:22 ` Dave Jiang
2022-11-21 14:25 ` Marek Bykowski
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=Y3bW8CLw8xcbrfav@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=marek.bykowski@gmail.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