From: Dave Jiang <dave.jiang@intel.com>
To: Marek Bykowski <marek.bykowski@gmail.com>,
Alison Schofield <alison.schofield@intel.com>
Cc: linux-cxl@vger.kernel.org
Subject: Re: trace events
Date: Fri, 18 Nov 2022 08:18:43 -0700 [thread overview]
Message-ID: <c71a8cea-b2d1-8190-51d0-754f80aa96a0@intel.com> (raw)
In-Reply-To: <20221118135311.12cb241d@ubuntu.armcompdev.pub.tds.tieto.com>
On 11/18/2022 6:53 AM, Marek Bykowski wrote:
> On Thu, 17 Nov 2022 16:50:56 -0800
> Alison Schofield <alison.schofield@intel.com> wrote:
>
>> 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?
>
> Hi Alison,
>
> There should be already plenty of tools using the trace events,
> libtraceevent, libtrracefs and trace-cmd, lttng, but I guess
> another one may be of use too. When do you think it should be out
> for testing?
>
> For the project, it is strictly secret, and I shouldn't reveal too
> much publicly, as I was told at least, but what we do we basically
> test a CXL root complex in RTL/verilog that instead of being synthesized,
> gets compiled to a VCS sim (a simulator) that in turn gets
> connected through the BFM (bus-function-model) to another simulator,
> simics or qemu. The connection to another simulator is for having
> the root complex to test it against something.
>
> So to serve the purpose I need a good grip at what is happening at
> a very low level, ideally with the CXL operation taken down to the
> register access/mnemonics, especially throughout the enumeration
> phase, which we think will the primary source of all the defects to be
> caught up and fixed in RTL.
>
> I hope our paths would cross at some point in which the HW will be
> finding its way to Linux with all the support it requires.
>
> Any tips/suggestions how I can use Linux for now effectively to
> achieve my goals is highly appreciated.
Hi Marek. Have you looked into enabling ftrace? Maybe that would be the
right starting point for what you are looking for?
https://lwn.net/Articles/365835/
>
> Thanks,
> Marek
next prev parent reply other threads:[~2022-11-18 15:18 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
2022-11-18 13:53 ` Marek Bykowski
2022-11-18 15:18 ` Dave Jiang [this message]
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=c71a8cea-b2d1-8190-51d0-754f80aa96a0@intel.com \
--to=dave.jiang@intel.com \
--cc=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 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.