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: "Williams, Dan J" <dan.j.williams@intel.com>,
"Schofield, Alison" <alison.schofield@intel.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"Weiny, Ira" <ira.weiny@intel.com>
Subject: Re: [PATCH v4 10/10] cxl: add man page documentation for monitor
Date: Wed, 9 Nov 2022 00:58:41 +0000 [thread overview]
Message-ID: <cc92e8defb8da60a60a1f0e9802e4b4d914f3912.camel@intel.com> (raw)
In-Reply-To: <166793224539.3768752.16520384828313781321.stgit@djiang5-desk3.ch.intel.com>
On Tue, 2022-11-08 at 11:30 -0700, Dave Jiang wrote:
> Add man page documentation to explain the usage of cxl monitor.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Documentation/cxl/cxl-monitor.txt | 77 +++++++++++++++++++++++++++++++++++++
Is this missing an update to a meson.build in Documentation/cxl?
> 1 file changed, 77 insertions(+)
> create mode 100644 Documentation/cxl/cxl-monitor.txt
>
> diff --git a/Documentation/cxl/cxl-monitor.txt b/Documentation/cxl/cxl-monitor.txt
> new file mode 100644
> index 000000000000..43c2ece72220
> --- /dev/null
> +++ b/Documentation/cxl/cxl-monitor.txt
> @@ -0,0 +1,77 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +cxl-monitor(1)
> +================
Unaligned '===' line
> +
> +NAME
> +----
> +cxl-monitor - Monitor the CXL kernel trace events
Probably drop 'kernel' here.
> +
> +SYNOPSIS
> +--------
> +[verse]
> +'cxl monitor' [<options>]
> +
> +DESCRIPTION
> +-----------
> +Cxl monitor is used for monitoring the CXL trace events emitted by
s/Cxl/CXL/ or s/Cxl monitor/cxl-monitor/ I think.
> +the kernel and convert them to json objects and dumping the json format
> +notifications to standard output or a logfile.
> +
> +Both, the values in configuration file and in options will work. If
s/file/file,/
Also is config file support actually present yet?
> +there is a conflict, the values in options will override the values in
> +the configuration file. Any updated values in the configuration file will
> +take effect only after the monitor process is restarted.
> +
> +EXAMPLES
> +--------
> +
> +Run a monitor as a daemon to monitor events and output to a log file.
> +[verse]
> +cxl monitor --daemon --log=/var/log/cxl-monitor.log
> +
> +Run a monitor as a one-shot command and output the notifications to stdio.
> +[verse]
> +cxl monitor
> +
> +Run a monitor daemon as a system service
> +[verse]
> +systemctl start cxl-monitor.service
> +
> +OPTIONS
> +-------
> +-l::
> +--log=::
> + Send log messages to the specified destination.
> + - "<file>":
> + Send log messages to specified <file>. When fopen() is not able
> + to open <file>, log messages will be forwarded to syslog.
> + - "standard":
> + Send messages to standard output.
> +
> +The default log destination is '/var/log/cxl-monitor.log' if "--daemon" is specified,
> +otherwise 'standard'. Note that standard and relative path for <file>
> +will not work if "--daemon" is specified.
> +
> +--daemon::
> + Run a monitor as a daemon.
> +
> +-u::
> +--human::
> + Output monitor notification as human friendly json format instead
> + of the default machine friendly json format.
> +
> +-v::
> +--verbose::
> + Emit extra debug messages to log.
> +
> +COPYRIGHT
> +---------
> +Copyright (c) 2022, Intel Corp. License GPLv2: GNU GPL version 2
> +<http://gnu.org/licenses/gpl.html>. This is free software: you are
> +free to change and redistribute it. There is NO WARRANTY, to the
> +extent permitted by law.
I think there is an include for the copyright under Documentation/cxl,
as well as for human and verbose options.
> +
> +SEE ALSO
> +--------
> +linkcxl:cxl-list[1]
>
>
prev parent reply other threads:[~2022-11-09 0:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 18:29 [PATCH v4 00/10] cxl: add monitor support for trace events Dave Jiang
2022-11-08 18:29 ` [PATCH v4 01/10] cxl: add helper function to parse trace event to json object Dave Jiang
2022-11-08 23:02 ` Verma, Vishal L
2022-11-09 21:27 ` Dave Jiang
2022-11-08 18:29 ` [PATCH v4 02/10] cxl: add helper to parse through all current events Dave Jiang
2022-11-08 23:45 ` Verma, Vishal L
2022-11-09 21:30 ` Dave Jiang
2022-11-08 18:30 ` [PATCH v4 03/10] cxl: add common function to enable event trace Dave Jiang
2022-11-08 18:30 ` [PATCH v4 04/10] cxl: add common function to disable " Dave Jiang
2022-11-08 23:47 ` Verma, Vishal L
2022-11-08 18:30 ` [PATCH v4 05/10] cxl: add monitor function for event trace events Dave Jiang
2022-11-17 18:37 ` Steven Rostedt
2022-11-17 20:29 ` Dave Jiang
2022-11-17 20:33 ` Steven Rostedt
2022-11-17 20:44 ` Dave Jiang
2022-11-08 18:30 ` [PATCH v4 06/10] cxl: add logging functions for monitor Dave Jiang
2022-11-09 0:31 ` Verma, Vishal L
2022-11-08 18:30 ` [PATCH v4 07/10] cxl: add monitor command to cxl Dave Jiang
2022-11-09 0:35 ` Verma, Vishal L
2022-11-08 18:30 ` [PATCH v4 08/10] cxl: add an optional pid check to event parsing Dave Jiang
2022-11-09 0:48 ` Verma, Vishal L
2022-11-09 22:44 ` Dave Jiang
2022-11-08 18:30 ` [PATCH v4 09/10] cxl: add systemd service for monitor Dave Jiang
2022-11-09 0:48 ` Verma, Vishal L
2022-11-08 18:30 ` [PATCH v4 10/10] cxl: add man page documentation " Dave Jiang
2022-11-09 0:58 ` Verma, Vishal L [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=cc92e8defb8da60a60a1f0e9802e4b4d914f3912.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=rostedt@goodmis.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