From: Dave Jiang <dave.jiang@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: linux-cxl@vger.kernel.org, dan.j.williams@intel.com,
ira.weiny@intel.com, vishal.l.verma@intel.com,
alison.schofield@intel.com, Jonathan.Cameron@huawei.com,
jgg@nvidia.com, shiju.jose@huawei.com,
Li Ming <ming.li@zohomail.com>
Subject: Re: [PATCH v7 02/14] cxl: Add Get Supported Features command for kernel usage
Date: Wed, 26 Feb 2025 08:31:58 -0700 [thread overview]
Message-ID: <d6eaed28-1a82-4cee-af00-002e556725fe@intel.com> (raw)
In-Reply-To: <20250225210016.vdci7r7pwseytsyr@offworld>
On 2/25/25 2:01 PM, Davidlohr Bueso wrote:
> On Thu, 20 Feb 2025, Dave Jiang wrote:
>
>> CXL spec r3.2 8.2.9.6.1 Get Supported Features (Opcode 0500h)
>> The command retrieve the list of supported device-specific features
>> (identified by UUID) and general information about each Feature.
>>
>> The driver will retrieve the Feature entries in order to make checks and
>> provide information for the Get Feature and Set Feature command. One of
>> the main piece of information retrieved are the effects a Set Feature
>> command would have for a particular feature. The retrieved Feature
>> entries are stored in the cxl_mailbox context.
>>
>> The setup of Features is initiated via devm_cxl_setup_features() during the
>> pci probe function before the cxl_memdev is enumerated.
>>
>> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
>> Reviewed-by: Li Ming <ming.li@zohomail.com>
>> Tested-by: Shiju Jose <shiju.jose@huawei.com>
>
> Reviewed-by: Davidlohr Bueso <dave@stgolabs.net>
>
> ... with a comment below.
>
>> +config CXL_FEATURES
>> + bool "CXL: Features"
>> + depends on CXL_PCI
>> + help
>> + Enable support for CXL Features. A CXL device that includes a mailbox
>> + supports commands that allows listing, getting, and setting of
>> + optionally defined features such as memory sparing or post package
>> + sparing. Vendors may define custom features for the device.
>> +
>> + If unsure say 'n'
>
> When would a user want to disable this (admittedly this might become clearer further
> into the series)? But it seems this should not be tucked behind a kconfig, much less
> default to off.
At this point probably when the user want a locked down kernel without fwctl support. Dan wanted the entire Features support behind a kconfig for now.
https://lore.kernel.org/linux-cxl/67a2b6d345b61_2d2c2943c@dwillia2-xfh.jf.intel.com.notmuch/
>
> Thanks,
> Davidlohr
next prev parent reply other threads:[~2025-02-26 15:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 19:42 [PATCH v7 00/14] cxl: Add CXL feature commands support via fwctl Dave Jiang
2025-02-20 19:42 ` [PATCH v7 01/14] cxl: Enumerate feature commands Dave Jiang
2025-02-25 21:09 ` Davidlohr Bueso
2025-02-20 19:42 ` [PATCH v7 02/14] cxl: Add Get Supported Features command for kernel usage Dave Jiang
2025-02-25 21:01 ` Davidlohr Bueso
2025-02-26 15:31 ` Dave Jiang [this message]
2025-02-20 19:42 ` [PATCH v7 03/14] cxl/test: Add Get Supported Features mailbox command support Dave Jiang
2025-02-20 19:42 ` [PATCH v7 04/14] cxl/mbox: Add GET_FEATURE mailbox command Dave Jiang
2025-02-20 19:42 ` [PATCH v7 05/14] cxl/mbox: Add SET_FEATURE " Dave Jiang
2025-02-20 19:42 ` [PATCH v7 06/14] cxl: Setup exclusive CXL features that are reserved for the kernel Dave Jiang
2025-02-20 19:42 ` [PATCH v7 07/14] cxl: Add FWCTL support to CXL Dave Jiang
2025-02-20 19:42 ` [PATCH v7 08/14] cxl: Move cxl feature command structs to user header Dave Jiang
2025-02-20 19:42 ` [PATCH v7 09/14] cxl: Add support for fwctl RPC command to enable CXL feature commands Dave Jiang
2025-02-20 19:42 ` [PATCH v7 10/14] cxl: Add support to handle user feature commands for get feature Dave Jiang
2025-02-20 19:42 ` [PATCH v7 11/14] cxl: Add support to handle user feature commands for set feature Dave Jiang
2025-02-20 19:42 ` [PATCH v7 12/14] cxl/test: Add Get Feature support to cxl_test Dave Jiang
2025-02-20 19:42 ` [PATCH v7 13/14] cxl/test: Add Set " Dave Jiang
2025-02-20 19:42 ` [PATCH v7 14/14] fwctl/cxl: Add documentation to FWCTL CXL Dave Jiang
2025-02-25 17:54 ` [PATCH v7 00/14] cxl: Add CXL feature commands support via fwctl Dave Jiang
2025-02-26 16:02 ` 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=d6eaed28-1a82-4cee-af00-002e556725fe@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