From: fan <nifan.cxl@gmail.com>
To: shiju.jose@huawei.com
Cc: qemu-devel@nongnu.org, linux-cxl@vger.kernel.org,
jonathan.cameron@huawei.com, tanxiaofei@huawei.com,
prime.zeng@hisilicon.com, linuxarm@huawei.com
Subject: Re: [PATCH v2 0/3] hw/cxl/cxl-mailbox-utils: Add feature commands, device patrol scrub control and DDR5 ECS control features
Date: Thu, 15 Feb 2024 10:08:33 -0800 [thread overview]
Message-ID: <Zc5TId-xVNl82xbJ@debian> (raw)
In-Reply-To: <20231124135338.1191-1-shiju.jose@huawei.com>
On Fri, Nov 24, 2023 at 09:53:34PM +0800, shiju.jose@huawei.com wrote:
> From: Shiju Jose <shiju.jose@huawei.com>
>
> Add support for the feature commands, device patrol scrub control and
> DDR5 ECS control features.
>
> CXL spec 3.0 section 8.2.9.6 describes optional device specific features.
> CXL spec 3.1 section 8.2.9.9.11.1 describes the device patrol scrub control
> feature.
> CXL spec 3.1 section 8.2.9.9.11.2 describes the DDR5 Error Check Scrub (ECS)
> control feature.
>
> The patches are available here,
> https://gitlab.com/shiju.jose/qemu/-/tree/cxl-scrub-2023-11-14
> and is based on Jonathan's branch
> https://gitlab.com/jic23/qemu/-/tree/cxl-2023-10-16
>
> Changes
> v1 -> v2
> 1. Changes for Davidlohr comments. Thanks.
> - Changed CXL SET feature data transfer flags as enum.
> - Modified pointer supported_feats to get_feats_out.
> - Removed an unnecessary branch.
> - Use MIN().
> - Move setting of hdr.nsuppfeats further down.
> - Return CXL_MBOX_UNSUPPORTED if non-zero selection flag is passed.
> - Add more IMMEDIATE_*.* flags set_feature.
> - Corrected a spelling error.
>
> Shiju Jose (3):
> hw/cxl/cxl-mailbox-utils: Add support for feature commands (8.2.9.6)
> hw/cxl/cxl-mailbox-utils: Add device patrol scrub control feature
> hw/cxl/cxl-mailbox-utils: Add device DDR5 ECS control feature
>
> hw/cxl/cxl-mailbox-utils.c | 360 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 360 insertions(+)
>
> --
> 2.34.1
>
Recently, Jonathan has updated all the specification references to align
with cxl spec r3.1, so for the next version, we may want to also do
that.
Fan
next prev parent reply other threads:[~2024-02-15 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 13:53 [PATCH v2 0/3] hw/cxl/cxl-mailbox-utils: Add feature commands, device patrol scrub control and DDR5 ECS control features shiju.jose--- via
2023-11-24 13:53 ` [PATCH v2 1/3] hw/cxl/cxl-mailbox-utils: Add support for feature commands (8.2.9.6) shiju.jose--- via
2024-02-15 18:05 ` fan
2024-02-16 9:20 ` Shiju Jose via
2023-11-24 13:53 ` [PATCH v2 2/3] hw/cxl/cxl-mailbox-utils: Add device patrol scrub control feature shiju.jose--- via
2024-02-15 18:47 ` fan
2024-02-16 10:16 ` Shiju Jose via
2024-02-16 17:35 ` fan
2024-02-15 20:55 ` Davidlohr Bueso
2024-02-16 12:11 ` Shiju Jose via
2023-11-24 13:53 ` [PATCH v2 3/3] hw/cxl/cxl-mailbox-utils: Add device DDR5 ECS " shiju.jose--- via
2024-02-15 19:11 ` fan
2024-02-15 18:08 ` fan [this message]
2024-02-16 9:22 ` [PATCH v2 0/3] hw/cxl/cxl-mailbox-utils: Add feature commands, device patrol scrub control and DDR5 ECS control features Shiju Jose via
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=Zc5TId-xVNl82xbJ@debian \
--to=nifan.cxl@gmail.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=qemu-devel@nongnu.org \
--cc=shiju.jose@huawei.com \
--cc=tanxiaofei@huawei.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;
as well as URLs for NNTP newsgroup(s).