Linux CXL
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Jiang, Dave" <dave.jiang@intel.com>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Cc: "bwidawsk@kernel.org" <bwidawsk@kernel.org>,
	"Schofield, Alison" <alison.schofield@intel.com>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"Weiny, Ira" <ira.weiny@intel.com>
Subject: Re: [PATCH 0/7] ndctl: cxl: add monitor support for trace events
Date: Wed, 14 Sep 2022 23:04:11 +0000	[thread overview]
Message-ID: <c651fa1ff2366679d6d05a044178c7d6557568e4.camel@intel.com> (raw)
In-Reply-To: <d4ccbf2d-e068-d686-ca6d-2d6ecc25d17a@intel.com>

On Wed, 2022-09-14 at 15:19 -0700, Dave Jiang wrote:
> 
> On 9/14/2022 1:47 PM, Dave Jiang 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.
> > 
> > ---
> > 
> > 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
> 
> Missing man page and systemd service. Will add in v2. Also will add 
> default log file path when running in daemon mode.

Haven't started looking at the rest, but I'll quickly add that no need
to include the 'ndctl:' prefix for these. 'cxl:' (or 'libcxl:' for
library patches) should be enough.

> > 
> >   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-14 23:04 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 [this message]
2022-09-22 14:21 ` Jonathan Cameron
2022-09-22 14:45   ` 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=c651fa1ff2366679d6d05a044178c7d6557568e4.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=bwidawsk@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    /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