From: Davidlohr Bueso <dave@stgolabs.net>
To: shiju.jose@huawei.com
Cc: linux-cxl@vger.kernel.org, linux-mm@kvack.org,
jonathan.cameron@huawei.com, dave.jiang@intel.com,
alison.schofield@intel.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, dan.j.williams@intel.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
david@redhat.com, Vilas.Sridharan@amd.com, leo.duran@amd.com,
Yazen.Ghannam@amd.com, rientjes@google.com, jiaqiyan@google.com,
tony.luck@intel.com, Jon.Grimm@amd.com,
dave.hansen@linux.intel.com, rafael@kernel.org, lenb@kernel.org,
naoya.horiguchi@nec.com, james.morse@arm.com,
jthoughton@google.com, somasundaram.a@hpe.com,
erdemaktas@google.com, pgonda@google.com, duenwen@google.com,
mike.malvestuto@intel.com, gthelen@google.com,
wschwartz@amperecomputing.com, dferguson@amperecomputing.com,
tanxiaofei@huawei.com, prime.zeng@hisilicon.com,
kangkang.shen@futurewei.com, wanghuiqiang@huawei.com,
linuxarm@huawei.com, fan.ni@samsung.com,
a.manzanares@samsung.com
Subject: Re: [PATCH v2 03/10] cxl/mbox: Add SET_FEATURE mailbox command
Date: Tue, 21 Nov 2023 17:01:14 -0800 [thread overview]
Message-ID: <l6spiq3w45fwswuz4adrhhll2w52sc3vj2gg57kys5aaulo6v4@i4pbbjzhm3aq> (raw)
In-Reply-To: <20231121101844.1161-4-shiju.jose@huawei.com>
On Tue, 21 Nov 2023, shiju.jose@huawei.com wrote:
>From: Shiju Jose <shiju.jose@huawei.com>
>
>Add support for SET_FEATURE mailbox command.
>
>CXL spec 3.0 section 8.2.9.6 describes optional device specific features.
>CXL devices supports features with changeable attributes.
>The settings of a feature can be optionally modified using Set Feature
>command.
>
>Signed-off-by: Shiju Jose <shiju.jose@huawei.com>
>---
> drivers/cxl/core/mbox.c | 15 +++++++++++++++
> drivers/cxl/cxlmem.h | 27 +++++++++++++++++++++++++++
> include/uapi/linux/cxl_mem.h | 1 +
> 3 files changed, 43 insertions(+)
>
>diff --git a/drivers/cxl/core/mbox.c b/drivers/cxl/core/mbox.c
>index 2675c616caec..d892b07446ca 100644
>--- a/drivers/cxl/core/mbox.c
>+++ b/drivers/cxl/core/mbox.c
>@@ -65,6 +65,7 @@ static struct cxl_mem_command cxl_mem_commands[CXL_MEM_COMMAND_ID_MAX] = {
> CXL_CMD(GET_SCAN_MEDIA_CAPS, 0x10, 0x4, 0),
> CXL_CMD(GET_SUPPORTED_FEATURES, 0x8, CXL_VARIABLE_PAYLOAD, 0),
> CXL_CMD(GET_FEATURE, 0x15, CXL_VARIABLE_PAYLOAD, 0),
>+ CXL_CMD(SET_FEATURE, CXL_VARIABLE_PAYLOAD, 0, 0),
> };
>
> /*
>@@ -1350,6 +1351,20 @@ int cxl_get_feature(struct cxl_memdev_state *mds,
> }
> EXPORT_SYMBOL_NS_GPL(cxl_get_feature, CXL);
>
>+int cxl_set_feature(struct cxl_memdev_state *mds, void *feat_in, size_t size)
>+{
>+ struct cxl_mbox_cmd mbox_cmd;
>+
>+ mbox_cmd = (struct cxl_mbox_cmd) {
>+ .opcode = CXL_MBOX_OP_SET_FEATURE,
>+ .size_in = size,
>+ .payload_in = feat_in,
>+ };
>+
>+ return cxl_internal_send_cmd(mds, &mbox_cmd);
>+}
>+EXPORT_SYMBOL_NS_GPL(cxl_set_feature, CXL);
>+
> int cxl_mem_get_poison(struct cxl_memdev *cxlmd, u64 offset, u64 len,
> struct cxl_region *cxlr)
> {
>diff --git a/drivers/cxl/cxlmem.h b/drivers/cxl/cxlmem.h
>index 92c1f2a44713..46131dcd0900 100644
>--- a/drivers/cxl/cxlmem.h
>+++ b/drivers/cxl/cxlmem.h
>@@ -508,6 +508,7 @@ enum cxl_opcode {
> CXL_MBOX_OP_GET_LOG = 0x0401,
> CXL_MBOX_OP_GET_SUPPORTED_FEATURES = 0x0500,
> CXL_MBOX_OP_GET_FEATURE = 0x0501,
>+ CXL_MBOX_OP_SET_FEATURE = 0x0502,
> CXL_MBOX_OP_IDENTIFY = 0x4000,
> CXL_MBOX_OP_GET_PARTITION_INFO = 0x4100,
> CXL_MBOX_OP_SET_PARTITION_INFO = 0x4101,
>@@ -817,6 +818,31 @@ struct cxl_mbox_get_feat_in {
> u8 selection;
> } __packed;
>
>+/* Set Feature CXL 3.0 Spec 8.2.9.6.3 */
>+/*
>+ * Set Feature input payload
>+ * CXL rev 3.0 section 8.2.9.6.3; Table 8-81
>+ */
>+/* Set Feature : Payload in flags */
>+#define CXL_SET_FEAT_FLAG_DATA_TRANSFER_MASK GENMASK(2, 0)
>+enum cxl_set_feat_flag_data_transfer {
>+ CXL_SET_FEAT_FLAG_FULL_DATA_TRANSFER = 0x0,
>+ CXL_SET_FEAT_FLAG_INITIATE_DATA_TRANSFER = 0x1,
>+ CXL_SET_FEAT_FLAG_CONTINUE_DATA_TRANSFER = 0x2,
>+ CXL_SET_FEAT_FLAG_FINISH_DATA_TRANSFER = 0x3,
>+ CXL_SET_FEAT_FLAG_ABORT_DATA_TRANSFER = 0x4,
>+ CXL_SET_FEAT_FLAG_DATA_TRANSFER_MAX
>+};
>+#define CXL_SET_FEAT_FLAG_MOD_VALUE_SAVED_ACROSS_RESET BIT(3)
>+
>+struct cxl_mbox_set_feat_in {
>+ uuid_t uuid;
>+ __le32 flags;
>+ __le16 offset;
>+ u8 version;
>+ u8 rsvd[9];
>+} __packed;
>+
> /* Get Poison List CXL 3.0 Spec 8.2.9.8.4.1 */
> struct cxl_mbox_poison_in {
> __le64 offset;
>@@ -949,6 +975,7 @@ int cxl_get_supported_features(struct cxl_memdev_state *mds,
> void *feats_out);
> int cxl_get_feature(struct cxl_memdev_state *mds,
> struct cxl_mbox_get_feat_in *pi, void *feat_out);
>+int cxl_set_feature(struct cxl_memdev_state *mds, void *feat_in, size_t size);
> int cxl_poison_state_init(struct cxl_memdev_state *mds);
> int cxl_mem_get_poison(struct cxl_memdev *cxlmd, u64 offset, u64 len,
> struct cxl_region *cxlr);
>diff --git a/include/uapi/linux/cxl_mem.h b/include/uapi/linux/cxl_mem.h
>index b20de60bfc71..8c89d323cc41 100644
>--- a/include/uapi/linux/cxl_mem.h
>+++ b/include/uapi/linux/cxl_mem.h
>@@ -48,6 +48,7 @@
> ___DEPRECATED(GET_SCAN_MEDIA, "Get Scan Media Results"), \
> ___C(GET_SUPPORTED_FEATURES, "Get Supported Features"), \
> ___C(GET_FEATURE, "Get Feature"), \
>+ ___C(SET_FEATURE, "Set Feature"), \
I don't think we want to export this to userspace, and you are
already using the scrub driver for setting feat attributes.
> ___C(MAX, "invalid / last command")
>
> #define ___C(a, b) CXL_MEM_COMMAND_ID_##a
>--
>2.34.1
>
next prev parent reply other threads:[~2023-11-22 1:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 10:18 [PATCH v2 00/10] cxl: Add support for CXL feature commands, CXL device patrol scrub control and DDR5 ECS control features shiju.jose
2023-11-21 10:18 ` [PATCH v2 01/10] cxl/mbox: Add GET_SUPPORTED_FEATURES mailbox command shiju.jose
2023-11-21 21:27 ` kernel test robot
2023-11-22 0:04 ` kernel test robot
2023-11-21 10:18 ` [PATCH v2 02/10] cxl/mbox: Add GET_FEATURE " shiju.jose
2023-11-21 22:52 ` kernel test robot
2023-11-22 2:10 ` kernel test robot
2023-11-21 10:18 ` [PATCH v2 03/10] cxl/mbox: Add SET_FEATURE " shiju.jose
2023-11-22 1:01 ` Davidlohr Bueso [this message]
2023-11-21 10:18 ` [PATCH v2 04/10] cxl/memscrub: Add CXL device patrol scrub control feature shiju.jose
2023-11-22 0:21 ` Davidlohr Bueso
2023-11-22 9:48 ` Shiju Jose
2023-11-22 12:40 ` kernel test robot
2023-11-21 10:18 ` [PATCH v2 05/10] cxl/memscrub: Add CXL device DDR5 ECS " shiju.jose
2023-11-21 10:18 ` [PATCH v2 06/10] memory: scrub: Add scrub driver supports configuring memory scrubbers in the system shiju.jose
2023-11-22 1:59 ` kernel test robot
2023-11-22 10:42 ` Dan Carpenter
2023-11-21 10:18 ` [PATCH v2 07/10] cxl/memscrub: Register CXL device patrol scrub with scrub configure driver shiju.jose
2023-11-22 7:19 ` kernel test robot
2023-11-21 10:18 ` [PATCH v2 08/10] memory: scrub: Add scrub control attributes for the DDR5 ECS shiju.jose
2023-11-21 10:18 ` [PATCH v2 09/10] cxl/memscrub: Register CXL device DDR5 ECS with scrub configure driver shiju.jose
2023-11-21 10:18 ` [PATCH v2 10/10] cxl: scrub: sysfs: Add Documentation for CXL memory device scrub control attributes shiju.jose
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=l6spiq3w45fwswuz4adrhhll2w52sc3vj2gg57kys5aaulo6v4@i4pbbjzhm3aq \
--to=dave@stgolabs.net \
--cc=Jon.Grimm@amd.com \
--cc=Vilas.Sridharan@amd.com \
--cc=Yazen.Ghannam@amd.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=david@redhat.com \
--cc=dferguson@amperecomputing.com \
--cc=duenwen@google.com \
--cc=erdemaktas@google.com \
--cc=fan.ni@samsung.com \
--cc=gthelen@google.com \
--cc=ira.weiny@intel.com \
--cc=james.morse@arm.com \
--cc=jiaqiyan@google.com \
--cc=jonathan.cameron@huawei.com \
--cc=jthoughton@google.com \
--cc=kangkang.shen@futurewei.com \
--cc=lenb@kernel.org \
--cc=leo.duran@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=mike.malvestuto@intel.com \
--cc=naoya.horiguchi@nec.com \
--cc=pgonda@google.com \
--cc=prime.zeng@hisilicon.com \
--cc=rafael@kernel.org \
--cc=rientjes@google.com \
--cc=shiju.jose@huawei.com \
--cc=somasundaram.a@hpe.com \
--cc=tanxiaofei@huawei.com \
--cc=tony.luck@intel.com \
--cc=vishal.l.verma@intel.com \
--cc=wanghuiqiang@huawei.com \
--cc=wschwartz@amperecomputing.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