From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Fan Ni <fan.ni@samsung.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"gregory.price@memverge.com" <gregory.price@memverge.com>,
"hchkuo@avery-design.com.tw" <hchkuo@avery-design.com.tw>,
"cbrowy@avery-design.com" <cbrowy@avery-design.com>,
"ira.weiny@intel.com" <ira.weiny@intel.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
Adam Manzanares <a.manzanares@samsung.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"nmtadam.samsung@gmail.com" <nmtadam.samsung@gmail.com>,
"nifan@outlook.com" <nifan@outlook.com>
Subject: Re: [RFC 1/7] hw/cxl/cxl-mailbox-utils: Add dc_event_log_size field to output payload of identify memory device command
Date: Mon, 15 May 2023 14:02:42 +0100 [thread overview]
Message-ID: <20230515140242.00006764@Huawei.com> (raw)
In-Reply-To: <20230511175609.2091136-2-fan.ni@samsung.com>
On Thu, 11 May 2023 17:56:40 +0000
Fan Ni <fan.ni@samsung.com> wrote:
> From: Fan Ni <nifan@outlook.com>
>
> Based on CXL spec 3.0 Table 8-94 (Identify Memory Device Output
> Payload), dynamic capacity event log size should be part of
> output of the Identify command.
> Add dc_event_log_size to the output payload for the host to get the info.
>
> Signed-off-by: Fan Ni <fan.ni@samsung.com>
Trivial formatting aside, looks good to me.
Jonathan
> ---
> hw/cxl/cxl-mailbox-utils.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/hw/cxl/cxl-mailbox-utils.c b/hw/cxl/cxl-mailbox-utils.c
> index 9f8e6722d7..7ff4fbdf22 100644
> --- a/hw/cxl/cxl-mailbox-utils.c
> +++ b/hw/cxl/cxl-mailbox-utils.c
> @@ -21,6 +21,8 @@
> #include "sysemu/hostmem.h"
>
> #define CXL_CAPACITY_MULTIPLIER (256 * MiB)
> +/* Experimental value: dynamic capacity event log size */
> +#define CXL_DC_EVENT_LOG_SIZE 8
>
> /*
> * How to add a new command, example. The command set FOO, with cmd BAR.
> @@ -519,8 +521,9 @@ static CXLRetCode cmd_identify_memory_device(struct cxl_cmd *cmd,
> uint16_t inject_poison_limit;
> uint8_t poison_caps;
> uint8_t qos_telemetry_caps;
> + uint16_t dc_event_log_size;
Qemu uses 4 space indentation not tabs.
> } QEMU_PACKED *id;
> - QEMU_BUILD_BUG_ON(sizeof(*id) != 0x43);
> + QEMU_BUILD_BUG_ON(sizeof(*id) != 0x45);
>
> CXLType3Dev *ct3d = container_of(cxl_dstate, CXLType3Dev, cxl_dstate);
> CXLType3Class *cvc = CXL_TYPE3_GET_CLASS(ct3d);
> @@ -543,6 +546,7 @@ static CXLRetCode cmd_identify_memory_device(struct cxl_cmd *cmd,
> st24_le_p(id->poison_list_max_mer, 256);
> /* No limit - so limited by main poison record limit */
> stw_le_p(&id->inject_poison_limit, 0);
> + stw_le_p(&id->dc_event_log_size, CXL_DC_EVENT_LOG_SIZE);
>
> *len = sizeof(*id);
> return CXL_MBOX_SUCCESS;
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Fan Ni <fan.ni@samsung.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"gregory.price@memverge.com" <gregory.price@memverge.com>,
"hchkuo@avery-design.com.tw" <hchkuo@avery-design.com.tw>,
"cbrowy@avery-design.com" <cbrowy@avery-design.com>,
"ira.weiny@intel.com" <ira.weiny@intel.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
Adam Manzanares <a.manzanares@samsung.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"nmtadam.samsung@gmail.com" <nmtadam.samsung@gmail.com>,
"nifan@outlook.com" <nifan@outlook.com>
Subject: Re: [RFC 1/7] hw/cxl/cxl-mailbox-utils: Add dc_event_log_size field to output payload of identify memory device command
Date: Mon, 15 May 2023 14:02:42 +0100 [thread overview]
Message-ID: <20230515140242.00006764@Huawei.com> (raw)
In-Reply-To: <20230511175609.2091136-2-fan.ni@samsung.com>
On Thu, 11 May 2023 17:56:40 +0000
Fan Ni <fan.ni@samsung.com> wrote:
> From: Fan Ni <nifan@outlook.com>
>
> Based on CXL spec 3.0 Table 8-94 (Identify Memory Device Output
> Payload), dynamic capacity event log size should be part of
> output of the Identify command.
> Add dc_event_log_size to the output payload for the host to get the info.
>
> Signed-off-by: Fan Ni <fan.ni@samsung.com>
Trivial formatting aside, looks good to me.
Jonathan
> ---
> hw/cxl/cxl-mailbox-utils.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/hw/cxl/cxl-mailbox-utils.c b/hw/cxl/cxl-mailbox-utils.c
> index 9f8e6722d7..7ff4fbdf22 100644
> --- a/hw/cxl/cxl-mailbox-utils.c
> +++ b/hw/cxl/cxl-mailbox-utils.c
> @@ -21,6 +21,8 @@
> #include "sysemu/hostmem.h"
>
> #define CXL_CAPACITY_MULTIPLIER (256 * MiB)
> +/* Experimental value: dynamic capacity event log size */
> +#define CXL_DC_EVENT_LOG_SIZE 8
>
> /*
> * How to add a new command, example. The command set FOO, with cmd BAR.
> @@ -519,8 +521,9 @@ static CXLRetCode cmd_identify_memory_device(struct cxl_cmd *cmd,
> uint16_t inject_poison_limit;
> uint8_t poison_caps;
> uint8_t qos_telemetry_caps;
> + uint16_t dc_event_log_size;
Qemu uses 4 space indentation not tabs.
> } QEMU_PACKED *id;
> - QEMU_BUILD_BUG_ON(sizeof(*id) != 0x43);
> + QEMU_BUILD_BUG_ON(sizeof(*id) != 0x45);
>
> CXLType3Dev *ct3d = container_of(cxl_dstate, CXLType3Dev, cxl_dstate);
> CXLType3Class *cvc = CXL_TYPE3_GET_CLASS(ct3d);
> @@ -543,6 +546,7 @@ static CXLRetCode cmd_identify_memory_device(struct cxl_cmd *cmd,
> st24_le_p(id->poison_list_max_mer, 256);
> /* No limit - so limited by main poison record limit */
> stw_le_p(&id->inject_poison_limit, 0);
> + stw_le_p(&id->dc_event_log_size, CXL_DC_EVENT_LOG_SIZE);
>
> *len = sizeof(*id);
> return CXL_MBOX_SUCCESS;
next prev parent reply other threads:[~2023-05-15 13:02 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230511175641uscas1p2b1877f9179709b69e293acdd7e57104c@uscas1p2.samsung.com>
2023-05-11 17:56 ` [Qemu RFC 0/7] Early enabling of DCD emulation in Qemu Fan Ni
2023-05-11 17:56 ` [RFC 6/7] Add qmp interfaces to add/release dynamic capacity extents Fan Ni
2023-05-15 14:53 ` Jonathan Cameron
2023-05-15 14:53 ` Jonathan Cameron via
2023-05-11 17:56 ` [RFC 1/7] hw/cxl/cxl-mailbox-utils: Add dc_event_log_size field to output payload of identify memory device command Fan Ni
2023-05-15 13:02 ` Jonathan Cameron [this message]
2023-05-15 13:02 ` Jonathan Cameron via
2023-05-11 17:56 ` [RFC 5/7] hw/cxl/cxl-mailbox-utils: Add mailbox commands to support add/release dynamic capacity response Fan Ni
2023-05-15 14:37 ` Jonathan Cameron
2023-05-15 14:37 ` Jonathan Cameron via
2023-06-30 19:34 ` nifan
2023-05-11 17:56 ` [RFC 2/7] hw/cxl/cxl-mailbox-utils: Add dynamic capacity region representative and mailbox command support Fan Ni
2023-05-11 21:53 ` Nathan Fontenot
2023-05-15 13:58 ` Jonathan Cameron
2023-05-15 13:58 ` Jonathan Cameron via
2023-06-27 21:13 ` nifan
2023-05-15 13:54 ` Jonathan Cameron
2023-05-15 13:54 ` Jonathan Cameron via
2023-05-11 17:56 ` [RFC 7/7] hw/mem/cxl_type3: add read/write support to dynamic capacity Fan Ni
2023-05-15 15:22 ` Jonathan Cameron
2023-05-15 15:22 ` Jonathan Cameron via
2023-06-28 17:09 ` nifan
2023-07-03 1:33 ` Jonathan Cameron
2023-07-03 1:33 ` Jonathan Cameron via
2023-05-11 17:56 ` [RFC 4/7] hw/mem/cxl_type3: Add DC extent representative to cxl type3 device Fan Ni
2023-05-12 18:09 ` Nathan Fontenot
2023-05-15 14:09 ` Jonathan Cameron
2023-05-15 14:09 ` Jonathan Cameron via
2023-05-11 17:56 ` [RFC 3/7] hw/mem/cxl_type3: Add a parameter to pass number of DC regions the device supports in qemu command line Fan Ni
2023-05-15 14:03 ` Jonathan Cameron
2023-05-15 14:03 ` Jonathan Cameron via
2023-05-15 13:00 ` [Qemu RFC 0/7] Early enabling of DCD emulation in Qemu Jonathan Cameron
2023-05-15 13:00 ` Jonathan Cameron via
2023-05-16 14:39 ` Singh, Navneet
2023-06-27 20:52 ` nifan
2023-06-05 17:35 ` Ira Weiny
2023-06-05 17:51 ` Fan Ni
2023-06-07 18:13 ` Shesha Bhushan Sreenivasamurthy
2023-06-07 18:31 ` Fan Ni
2023-06-07 18:52 ` Shesha Bhushan Sreenivasamurthy
2023-06-08 9:43 ` Jonathan Cameron
2023-06-08 9:43 ` Jonathan Cameron via
2023-06-08 15:20 ` [EXT] " Shesha Bhushan Sreenivasamurthy
2023-06-08 16:55 ` Shesha Bhushan Sreenivasamurthy
2023-06-08 15:43 ` Ira Weiny
2023-06-08 18:10 ` nifan
2023-06-09 21:06 ` Ira Weiny
2023-06-10 0:28 ` [EXT] " Shesha Bhushan Sreenivasamurthy
2023-07-24 17:19 ` Fan Ni
2023-07-25 15:18 ` Ira Weiny
2023-07-25 16:46 ` Fan Ni
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=20230515140242.00006764@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=cbrowy@avery-design.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=gregory.price@memverge.com \
--cc=hchkuo@avery-design.com.tw \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nifan@outlook.com \
--cc=nmtadam.samsung@gmail.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.