From: Dave Jiang <dave.jiang@intel.com>
To: Li Ming <ming.li@zohomail.com>, linux-cxl@vger.kernel.org
Cc: dan.j.williams@intel.com, ira.weiny@intel.com,
vishal.l.verma@intel.com, alison.schofield@intel.com,
Jonathan.Cameron@huawei.com, dave@stgolabs.net, jgg@nvidia.com,
shiju.jose@huawei.com
Subject: Re: [PATCH v4 06/15] cxl: Setup exclusive CXL features that are reserved for the kernel
Date: Tue, 11 Feb 2025 09:13:58 -0700 [thread overview]
Message-ID: <56f7d17d-1a9f-4f97-8ca6-bc0206dc7f93@intel.com> (raw)
In-Reply-To: <7e199f67-f068-42fd-ae2e-fa2d402f9e20@zohomail.com>
On 2/10/25 10:46 PM, Li Ming wrote:
> On 2/11/2025 1:50 AM, Dave Jiang wrote:
>>
>> On 2/7/25 11:22 PM, Li Ming wrote:
>>> On 2/8/2025 7:37 AM, Dave Jiang wrote:
>>>> Certain features will be exclusively used by components such as in
>>>> kernel RAS driver. Setup an exclusion list that can be later filtered
>>>> out before exposing to user space.
>>>>
>>>> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>>>> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
>>>> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
>>>> ---
>>>> drivers/cxl/core/features.c | 26 ++++++++++++++++++++++++++
>>>> include/cxl/features.h | 34 ++++++++++++++++++++++++++++++++++
>>>> 2 files changed, 60 insertions(+)
>>>>
>>>> diff --git a/drivers/cxl/core/features.c b/drivers/cxl/core/features.c
>>>> index d337224158fa..82f21f64452a 100644
>>>> --- a/drivers/cxl/core/features.c
>>>> +++ b/drivers/cxl/core/features.c
>>>> @@ -6,6 +6,28 @@
>>>> #include "cxl.h"
>>>> #include "cxlmem.h"
>>>>
>>>> +/* All the features below are exclusive to the kernel */
>>>> +static const uuid_t cxl_exclusive_feats[] = {
>>>> + CXL_FEAT_PATROL_SCRUB_UUID,
>>>> + CXL_FEAT_ECS_UUID,
>>>> + CXL_FEAT_SPPR_UUID,
>>>> + CXL_FEAT_HPPR_UUID,
>>>> + CXL_FEAT_CACHELINE_SPARING_UUID,
>>>> + CXL_FEAT_ROW_SPARING_UUID,
>>>> + CXL_FEAT_BANK_SPARING_UUID,
>>>> + CXL_FEAT_RANK_SPARING_UUID,
>>>> +};
>>>> +
>>>> +static bool is_cxl_feature_exclusive(struct cxl_feat_entry *entry)
>>>> +{
>>>> + for (int i = 0; i < ARRAY_SIZE(cxl_exclusive_feats); i++) {
>>>> + if (uuid_equal(&entry->uuid, &cxl_exclusive_feats[i]))
>>>> + return true;
>>>> + }
>>>> +
>>>> + return false;
>>>> +}
>>>> +
>>>> inline struct cxl_features_state *to_cxlfs(struct cxl_dev_state *cxlds)
>>>> {
>>>> return cxlds->cxlfs;
>>>> @@ -46,6 +68,7 @@ get_supported_features(struct cxl_features_state *cxlfs)
>>>> struct cxl_mbox_get_sup_feats_in mbox_in;
>>>> struct cxl_feat_entry *entry;
>>>> struct cxl_mbox_cmd mbox_cmd;
>>>> + int user_feats = 0;
>>>> int count;
>>>>
>>>> count = cxl_get_supported_features_count(cxl_mbox);
>>>> @@ -120,6 +143,8 @@ get_supported_features(struct cxl_features_state *cxlfs)
>>>> return NULL;
>>>>
>>>> memcpy(entry, mbox_out->ents, retrieved);
>> While you are pointing out the issue with copying multiple entries, I noticed that this needs to be fixed in patch2 as well. It should be:
>> memcpy(entry, mbox_out->ents + start, retrieved);
>>
>> DJ
>
> I noticed there is a 'mbox_in.start_idx = cpu_to_le16(start)' before sending GET_SUPPORTED_FEATURES command every time.
>
> I think the 'mbox_out->ents[0]' is the first feature info starting from 'start', so the change you mentioned is not needed?
Ah yep. Thanks.
>
>
> Ming
>
next prev parent reply other threads:[~2025-02-11 16:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 23:37 [PATCH v4 00/15] cxl: Add CXL feature commands support via fwctl Dave Jiang
2025-02-07 23:37 ` [PATCH v4 01/15] cxl: Enumerate feature commands Dave Jiang
2025-02-07 23:47 ` Dan Williams
2025-02-08 6:00 ` Li Ming
2025-02-11 17:05 ` Jonathan Cameron
2025-02-07 23:37 ` [PATCH v4 02/15] cxl: Add Get Supported Features command for kernel usage Dave Jiang
2025-02-07 23:56 ` Dan Williams
2025-02-10 17:03 ` Dave Jiang
2025-02-08 6:13 ` Li Ming
2025-02-10 17:06 ` Dave Jiang
2025-02-07 23:37 ` [PATCH v4 03/15] cxl/test: Add Get Supported Features mailbox command support Dave Jiang
2025-02-07 23:37 ` [PATCH v4 04/15] cxl/mbox: Add GET_FEATURE mailbox command Dave Jiang
2025-02-08 0:12 ` Dan Williams
2025-02-07 23:37 ` [PATCH v4 05/15] cxl/mbox: Add SET_FEATURE " Dave Jiang
2025-02-08 0:21 ` Dan Williams
2025-02-08 6:17 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 06/15] cxl: Setup exclusive CXL features that are reserved for the kernel Dave Jiang
2025-02-08 1:10 ` Dan Williams
2025-02-08 1:16 ` Dave Jiang
2025-02-08 6:22 ` Li Ming
2025-02-10 17:40 ` Dave Jiang
2025-02-10 17:50 ` Dave Jiang
2025-02-11 5:46 ` Li Ming
2025-02-11 16:13 ` Dave Jiang [this message]
2025-02-07 23:37 ` [PATCH v4 07/15] cxl: Add FWCTL support to CXL Dave Jiang
2025-02-08 1:24 ` Dan Williams
2025-02-07 23:37 ` [PATCH v4 08/15] cxl: Add support for FWCTL get driver information callback Dave Jiang
2025-02-08 1:25 ` Dan Williams
2025-02-10 6:21 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 09/15] cxl: Move cxl feature command structs to user header Dave Jiang
2025-02-07 23:37 ` [PATCH v4 10/15] cxl: Add support for fwctl RPC command to enable CXL feature commands Dave Jiang
2025-02-08 1:29 ` Dan Williams
2025-02-08 1:34 ` Dan Williams
2025-02-08 7:09 ` Li Ming
2025-02-10 22:31 ` Dave Jiang
2025-02-07 23:37 ` [PATCH v4 11/15] cxl: Add support to handle user feature commands for get feature Dave Jiang
2025-02-10 6:41 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 12/15] cxl: Add support to handle user feature commands for set feature Dave Jiang
2025-02-10 6:43 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 13/15] cxl/test: Add Get Feature support to cxl_test Dave Jiang
2025-02-10 6:44 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 14/15] cxl/test: Add Set " Dave Jiang
2025-02-10 6:44 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 15/15] fwctl/cxl: Add documentation to FWCTL CXL Dave Jiang
2025-02-08 1:38 ` Dan Williams
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=56f7d17d-1a9f-4f97-8ca6-bc0206dc7f93@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jgg@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=shiju.jose@huawei.com \
--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