From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "wzhang@meta.com" <wzhang@meta.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"Zhang, Jonathan" <jonzhang@fb.com>
Cc: "jonzhang@meta.com" <jonzhang@meta.com>
Subject: Re: [PATCH 1/2] libcxl: add accessors for Get Alert Configuration CCI command output
Date: Fri, 21 Oct 2022 07:30:22 +0000 [thread overview]
Message-ID: <653c03ca1601bae7b3490458a48c5d6ecbe69982.camel@intel.com> (raw)
In-Reply-To: <20221003232306.1326511-2-jonzhang@fb.com>
On Mon, 2022-10-03 at 16:23 -0700, Jonathan Zhang wrote:
> From: Jonathan Zhang <jonzhang@meta.com>
>
> CXL 3.0 spec section 8.2.9.8.3.2 "Get Alert Configuration
> (Opcode 4201h) defines the get-alert-config command to
> retrieve the devices's critical alert and programmable
> warning configuration.
>
> Add the methods to issue the command and get the fields
> defined.
>
> Signed-off-by: Jonathan Zhang <jonzhang@meta.com>
> ---
> Documentation/cxl/lib/libcxl.txt | 1 +
> cxl/lib/libcxl.c | 120 +++++++++++++++++++++++++++++++
> cxl/lib/libcxl.sym | 23 ++++++
> cxl/lib/private.h | 28 ++++++++
> cxl/libcxl.h | 19 +++++
> 5 files changed, 191 insertions(+)
Hi Jonathan,
Sorry for the delay in getting to these - a few small comments below.
>
> diff --git a/Documentation/cxl/lib/libcxl.txt b/Documentation/cxl/lib/libcxl.txt
> index fd2962a..dec3641 100644
> --- a/Documentation/cxl/lib/libcxl.txt
> +++ b/Documentation/cxl/lib/libcxl.txt
> @@ -121,6 +121,7 @@ information this call requires root / CAP_SYS_ADMIN.
> struct cxl_cmd *cxl_cmd_new_raw(struct cxl_memdev *memdev, int opcode);
> struct cxl_cmd *cxl_cmd_new_identify(struct cxl_memdev *memdev);
> struct cxl_cmd *cxl_cmd_new_get_health_info(struct cxl_memdev *memdev);
> +struct cxl_cmd *cxl_cmd_new_get_alert_config(struct cxl_memdev *memdev);
> struct cxl_cmd *cxl_cmd_new_read_label(struct cxl_memdev *memdev,
> unsigned int offset, unsigned int length);
> struct cxl_cmd *cxl_cmd_new_write_label(struct cxl_memdev *memdev, void *buf,
> diff --git a/cxl/lib/libcxl.c b/cxl/lib/libcxl.c
> index e8c5d44..ed5616c 100644
> --- a/cxl/lib/libcxl.c
> +++ b/cxl/lib/libcxl.c
> @@ -3140,6 +3140,126 @@ do { \
> return !!(c->field & mask); \
> } while(0)
>
> +CXL_EXPORT struct cxl_cmd *cxl_cmd_new_get_alert_config(
> + struct cxl_memdev *memdev)
> +{
> + return cxl_cmd_new_generic(memdev, CXL_MEM_COMMAND_ID_GET_ALERT_CONFIG);
> +}
> +
> +#define cmd_alert_get_valid_alerts_field(c, m) \
> + cmd_get_field_u8_mask(c, get_alert_config, GET_ALERT_CONFIG, valid_alerts, m)
> +
> +CXL_EXPORT int cxl_cmd_alert_config_get_life_used_prog_warn_threshold_valid(struct cxl_cmd *cmd)
Generally throughout these patches, because of the (unavoidably) long
names, these lines are well over 80 chars. For cases where a #define
for example can't be broken down further, that's okay. But a lot of
these can be split. We have a .clang-format for the project, and that
should do the right thing in all these cases.
<..>
>
> diff --git a/cxl/lib/libcxl.sym b/cxl/lib/libcxl.sym
> index 8bb91e0..7c1e261 100644
> --- a/cxl/lib/libcxl.sym
> +++ b/cxl/lib/libcxl.sym
> @@ -217,3 +217,26 @@ global:
> cxl_decoder_get_max_available_extent;
> cxl_decoder_get_region;
> } LIBCXL_2;
> +
> +LIBCXL_4 {
> +global:
> + cxl_cmd_new_get_alert_config;
> + cxl_cmd_alert_config_get_life_used_prog_warn_threshold_valid;
> + cxl_cmd_alert_config_get_dev_over_temp_prog_warn_threshold_valid;
> + cxl_cmd_alert_config_get_dev_under_temp_prog_warn_threshold_valid;
> + cxl_cmd_alert_config_get_corr_vol_mem_err_prog_warn_threshold_valid;
> + cxl_cmd_alert_config_get_corr_pers_mem_err_prog_warn_threshold_valid;
I think for all the 'valid' accessors, the 'get' can be dropped.
cxl_cmd_alert_config_<something>_valid is a reasonable API that asks
whether something is valid.
> + cxl_cmd_alert_config_get_life_used_prog_warn_threshold_prog;
> + cxl_cmd_alert_config_get_dev_over_temp_prog_warn_threshold_prog;
> + cxl_cmd_alert_config_get_dev_under_temp_prog_warn_threshold_prog;
> + cxl_cmd_alert_config_get_corr_vol_mem_err_prog_warn_threshold_prog;
> + cxl_cmd_alert_config_get_corr_pers_mem_err_prog_warn_threshold_prog;
> + cxl_cmd_alert_config_get_life_used_crit_alert_threshold;
> + cxl_cmd_alert_config_get_life_used_prog_warn_threshold;
> + cxl_cmd_alert_config_get_dev_over_temp_crit_alert_threshold;
> + cxl_cmd_alert_config_get_dev_under_temp_crit_alert_threshold;
> + cxl_cmd_alert_config_get_dev_over_temp_prog_warn_threshold;
> + cxl_cmd_alert_config_get_dev_under_temp_prog_warn_threshold;
> + cxl_cmd_alert_config_get_corr_vol_mem_err_prog_warn_threshold;
> + cxl_cmd_alert_config_get_corr_pers_mem_err_prog_warn_threshold;
These are okay to have the get, since we are getting a threshold value.
next prev parent reply other threads:[~2022-10-21 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 23:23 [ndctl PATCH 0/2] add support for CCI command Get Alert Configuration Jonathan Zhang
2022-10-03 23:23 ` [PATCH 1/2] libcxl: add accessors for Get Alert Configuration CCI command output Jonathan Zhang
2022-10-21 7:30 ` Verma, Vishal L [this message]
2022-10-21 7:35 ` Verma, Vishal L
2022-10-03 23:23 ` [PATCH 2/2] cxl: display alert configuratin fields in list command Jonathan Zhang
2022-10-21 7:30 ` Verma, Vishal L
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=653c03ca1601bae7b3490458a48c5d6ecbe69982.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=jonzhang@fb.com \
--cc=jonzhang@meta.com \
--cc=linux-cxl@vger.kernel.org \
--cc=wzhang@meta.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