Linux CXL
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: linux-cxl@vger.kernel.org, alison.schofield@intel.com,
	vishal.l.verma@intel.com, ira.weiny@intel.com,
	bwidawsk@kernel.org, dan.j.williams@intel.com
Subject: Re: [PATCH 0/7] ndctl: cxl: add monitor support for trace events
Date: Thu, 22 Sep 2022 07:45:27 -0700	[thread overview]
Message-ID: <d1906809-1c14-f19b-018c-9a6ae1614b82@intel.com> (raw)
In-Reply-To: <20220922152154.00007386@huawei.com>


On 9/22/2022 7:21 AM, Jonathan Cameron wrote:
> On Wed, 14 Sep 2022 13:47:49 -0700
> Dave Jiang <dave.jiang@intel.com> wrote:
>
>> This patch series for ndctl implements the monitor command for the cxl tool.
>> The initial implementation will collect CXL trace events emitted by the
>> kernel. libtraceevent and libtracefs will be used to parse the trace
>> event buffer. The monitor will pend on an epoll fd and wait for new event
>> entries to be posted. The output will be in json format. By default the events
>> are emitted to stdio, but can also be logged to a file. Each event is converted
>> to a JSON object and logged as such. All the fields exported are read by the
>> monitor code and added to the JSON object.
> Hi Dave,
>
> FYI, I just wanted to mention that we will be aiming to duplicate a bunch
> of this functionality in rasdaemon.
>
> As that is handling the equivalent of many of these events on our systems
> from other components we don't want to grab the data via alternative tooling
> and then have to merge it later.
>
> Absolutely not a problem to have it in this tool as well. I mostly wanted
> to raise it because longer term we'll need to be careful to test with both
> solutions if there are any changes to what they are being sent.

Thanks for the heads up Jonathan!


>
> Thanks,
>
> Jonathan
>
>> ---
>>
>> Dave Jiang (7):
>>        ndctl: cxl: add helper function to parse trace event to json object
>>        ndctl: cxl: add helper to parse through all current events
>>        ndctl: cxl: add common function to enable event trace
>>        ndctl: cxl: add common function to disable event trace
>>        ndctl: cxl: add monitor function for event trace events
>>        ndctl: cxl: add logging functions for monitor
>>        ndctl: cxl: add monitor command to cxl
>>
>>
>>   cxl/builtin.h     |   1 +
>>   cxl/cxl.c         |   1 +
>>   cxl/event_trace.c | 236 ++++++++++++++++++++++++++++++++++++++++++++++
>>   cxl/event_trace.h |  23 +++++
>>   cxl/meson.build   |   4 +
>>   cxl/monitor.c     | 235 +++++++++++++++++++++++++++++++++++++++++++++
>>   meson.build       |   3 +
>>   7 files changed, 503 insertions(+)
>>   create mode 100644 cxl/event_trace.c
>>   create mode 100644 cxl/event_trace.h
>>   create mode 100644 cxl/monitor.c
>>
>> --
>>

      reply	other threads:[~2022-09-22 14:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 20:47 [PATCH 0/7] ndctl: cxl: add monitor support for trace events Dave Jiang
2022-09-14 20:47 ` [PATCH 1/7] ndctl: cxl: add helper function to parse trace event to json object Dave Jiang
2022-10-31 20:01   ` Alison Schofield
2022-10-31 21:37     ` Dave Jiang
2022-11-02 21:01       ` Ira Weiny
2022-09-14 20:48 ` [PATCH 2/7] ndctl: cxl: add helper to parse through all current events Dave Jiang
2022-10-31 20:05   ` Alison Schofield
2022-09-14 20:48 ` [PATCH 3/7] ndctl: cxl: add common function to enable event trace Dave Jiang
2022-09-14 20:48 ` [PATCH 4/7] ndctl: cxl: add common function to disable " Dave Jiang
2022-09-14 20:48 ` [PATCH 5/7] ndctl: cxl: add monitor function for event trace events Dave Jiang
2022-09-19 18:26   ` Alison Schofield
2022-09-14 20:48 ` [PATCH 6/7] ndctl: cxl: add logging functions for monitor Dave Jiang
2022-09-15 15:55   ` Nathan Fontenot
2022-09-15 16:02     ` Dave Jiang
2022-09-14 20:48 ` [PATCH 7/7] ndctl: cxl: add monitor command to cxl Dave Jiang
2022-09-14 22:19 ` [PATCH 0/7] ndctl: cxl: add monitor support for trace events Dave Jiang
2022-09-14 23:04   ` Verma, Vishal L
2022-09-22 14:21 ` Jonathan Cameron
2022-09-22 14:45   ` Dave Jiang [this message]

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=d1906809-1c14-f19b-018c-9a6ae1614b82@intel.com \
    --to=dave.jiang@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=bwidawsk@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=ira.weiny@intel.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