From: Shiju Jose <shiju.jose@huawei.com>
To: Shiju Jose <shiju.jose@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Borislav Petkov <bp@alien8.de>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"alison.schofield@intel.com" <alison.schofield@intel.com>,
"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>,
"ira.weiny@intel.com" <ira.weiny@intel.com>,
"david@redhat.com" <david@redhat.com>,
"Vilas.Sridharan@amd.com" <Vilas.Sridharan@amd.com>,
"leo.duran@amd.com" <leo.duran@amd.com>,
"Yazen.Ghannam@amd.com" <Yazen.Ghannam@amd.com>,
"rientjes@google.com" <rientjes@google.com>,
"jiaqiyan@google.com" <jiaqiyan@google.com>,
"Jon.Grimm@amd.com" <Jon.Grimm@amd.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"naoya.horiguchi@nec.com" <naoya.horiguchi@nec.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"jthoughton@google.com" <jthoughton@google.com>,
"somasundaram.a@hpe.com" <somasundaram.a@hpe.com>,
"erdemaktas@google.com" <erdemaktas@google.com>,
"pgonda@google.com" <pgonda@google.com>,
"duenwen@google.com" <duenwen@google.com>,
"gthelen@google.com" <gthelen@google.com>,
"wschwartz@amperecomputing.com" <wschwartz@amperecomputing.com>,
"dferguson@amperecomputing.com" <dferguson@amperecomputing.com>,
"wbs@os.amperecomputing.com" <wbs@os.amperecomputing.com>,
"nifan.cxl@gmail.com" <nifan.cxl@gmail.com>,
tanxiaofei <tanxiaofei@huawei.com>,
"Zengtao (B)" <prime.zeng@hisilicon.com>,
Roberto Sassu <roberto.sassu@huawei.com>,
"kangkang.shen@futurewei.com" <kangkang.shen@futurewei.com>,
wanghuiqiang <wanghuiqiang@huawei.com>,
Linuxarm <linuxarm@huawei.com>
Subject: RE: [PATCH v17 00/18] EDAC: Scrub: introduce generic EDAC RAS control feature driver + CXL/ACPI-RAS2 drivers
Date: Fri, 3 Jan 2025 19:17:13 +0000 [thread overview]
Message-ID: <216de8e0176441e29a656865fc31d336@huawei.com> (raw)
In-Reply-To: <747cb4c966604aaf84f6b9f2d54df02c@huawei.com>
>-----Original Message-----
>From: Shiju Jose <shiju.jose@huawei.com>
>Sent: 03 January 2025 18:33
>To: Dave Jiang <dave.jiang@intel.com>; Jonathan Cameron
><jonathan.cameron@huawei.com>; Borislav Petkov <bp@alien8.de>
>Cc: linux-edac@vger.kernel.org; linux-cxl@vger.kernel.org; linux-
>acpi@vger.kernel.org; linux-mm@kvack.org; linux-kernel@vger.kernel.org;
>tony.luck@intel.com; rafael@kernel.org; lenb@kernel.org;
>mchehab@kernel.org; dan.j.williams@intel.com; dave@stgolabs.net;
>alison.schofield@intel.com; vishal.l.verma@intel.com; ira.weiny@intel.com;
>david@redhat.com; Vilas.Sridharan@amd.com; leo.duran@amd.com;
>Yazen.Ghannam@amd.com; rientjes@google.com; jiaqiyan@google.com;
>Jon.Grimm@amd.com; dave.hansen@linux.intel.com;
>naoya.horiguchi@nec.com; james.morse@arm.com; jthoughton@google.com;
>somasundaram.a@hpe.com; erdemaktas@google.com; pgonda@google.com;
>duenwen@google.com; gthelen@google.com;
>wschwartz@amperecomputing.com; dferguson@amperecomputing.com;
>wbs@os.amperecomputing.com; nifan.cxl@gmail.com; tanxiaofei
><tanxiaofei@huawei.com>; Zengtao (B) <prime.zeng@hisilicon.com>; Roberto
>Sassu <roberto.sassu@huawei.com>; kangkang.shen@futurewei.com;
>wanghuiqiang <wanghuiqiang@huawei.com>; Linuxarm
><linuxarm@huawei.com>
>Subject: RE: [PATCH v17 00/18] EDAC: Scrub: introduce generic EDAC RAS
>control feature driver + CXL/ACPI-RAS2 drivers
>
[...]
>>
>>
>>On 1/3/25 6:02 AM, Jonathan Cameron wrote:
>>> On Fri, 3 Jan 2025 12:41:45 +0100
>>> Borislav Petkov <bp@alien8.de> wrote:
>>>
>>>> On Fri, Nov 22, 2024 at 06:03:57PM +0000, shiju.jose@huawei.com wrote:
>>>>> drivers/edac/Makefile | 1 +
>>>>> drivers/edac/ecs.c | 207 +++
>>>>> drivers/edac/edac_device.c | 183 ++
>>>>> drivers/edac/mem_repair.c | 492 +++++
>>>>> drivers/edac/scrub.c | 209 +++
>>>>> drivers/ras/Kconfig | 10 +
>>>>> drivers/ras/Makefile | 1 +
>>>>> drivers/ras/acpi_ras2.c | 385 ++++
>>>>> include/acpi/ras2_acpi.h | 45 +
>>>>> include/cxl/features.h | 48 +
>>>>> include/cxl/mailbox.h | 45 +-
>>>>> include/linux/edac.h | 238 +++
>>>>> include/uapi/linux/cxl_mem.h | 3 +
>>>>
>>>> So what's the plan here? Am I supposed to merge the EDAC/RAS bits
>>>> through the RAS tree and then give folks an immutable branch or how
>>>> do we want to proceed here?
>>>>
>>>
>>> Dave Jiang / Rafael, what would work best for the two of you?
>>>
>>> To me Boris' suggestion makes sense, particularly as that avoids the
>>> complexity of CXL get/set features being in multiple series.
>>>
>>> I think the split that would make sense is:
>>>
>>> EDAC immutable branch for:
>>> 1: EDAC: Add support for EDAC device features control
>>> 2: Add scrub control feature
>>> 3: EDAC: Add ECS control feature
>>> 15: EDAC: Add memory repair control feature
>>>
>>> ACPI merges EDAC immutable +
>>> 13: ACPI:RAS2: Add ACPI RAS2 driver
>>> 14: ras: mem: Add memory ACPI RAS2 driver
>>>
>>> CXL merges EDAC immutable +
>>> 4: cxl: Refactor user ioctl command path from mds to mailbox
>>> 5: cxl: Add Get Supported Features command for kernel usage
>>> 6: cxl/mbox: Add GET_FEATURE mailbox command
>>> 7: cxl: Add Get Feature command support for user submission
>>> 8: cxl/mbox: Add SET_FEATURE mailbox command
>>> 9: cxl: Add Set Feature command support for user submission
>>> 10: cxl: Add UUIDs for the CXL RAS features
>>> 11: cxl/memfeature: Add CXL memory device patrol scrub control
>>> feature
>>> 12: cxl/memfeature: Add CXL memory device ECS control feature
>>> 16: cxl/mbox: Add support for PERFORM_MAINTENANCE mailbox command
>>> 17: cxl/memfeature: Add CXL memory device soft PPR control feature
>>> 18: cxl/memfeature: Add CXL memory device memory sparing control
>>> feature
>>
>>That works for me.
>>
>>DJ
>>
>>>
>>> That does mean that the actual drivers/edac/ specific drivers land
>>> via the ACPI and CXL trees only, but without another layer of
>>> immutable branches we can't avoid that. Might cause merge conflicts
>>> in Kconfig/Makefiles but otherwise shouldn't be too bad.
>>>
>>> There is going to be some noise in documentation as examples are
>>> added to the docs with the actual drivers (whereas generic docs are
>>> introduced with the infrastructure). I think that will work out though.
>>> Shiju, could you spin this ordering up and check it all works
>>> (incorporating Dave's updates to the GET / SET feature)?
>
>Rebased, reordered and tested fine. Waiting for some information before
>sharing the updated patches.
Please find updated and reordered patches in
https://github.com/shijujose4/linux/tree/edac-enhancement-ras-features_v18
Please note that EDAC patches are the same as in v17 other than updated, the kernel version
to 6.14 in the documentation.
>
>>> > Thanks,
>>>
>>> Jonathan
>>
Thanks,
Shiju
next prev parent reply other threads:[~2025-01-03 19:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 18:03 shiju.jose
2024-11-22 18:03 ` [PATCH v17 01/18] EDAC: Add support for EDAC device features control shiju.jose
2024-11-22 18:03 ` [PATCH v17 02/18] EDAC: Add scrub control feature shiju.jose
2024-11-22 18:04 ` [PATCH v17 03/18] EDAC: Add ECS " shiju.jose
2024-11-22 18:04 ` [PATCH v17 04/18] cxl: Refactor user ioctl command path from mds to mailbox shiju.jose
2024-11-22 18:04 ` [PATCH v17 05/18] cxl: Add Get Supported Features command for kernel usage shiju.jose
2024-12-06 21:40 ` Dan Williams
2024-12-09 14:28 ` Shiju Jose
2024-12-11 17:58 ` Shiju Jose
2024-11-22 18:04 ` [PATCH v17 06/18] cxl/mbox: Add GET_FEATURE mailbox command shiju.jose
2024-11-22 18:04 ` [PATCH v17 07/18] cxl: Add Get Feature command support for user submission shiju.jose
2024-11-22 18:04 ` [PATCH v17 08/18] cxl/mbox: Add SET_FEATURE mailbox command shiju.jose
2024-11-22 18:04 ` [PATCH v17 09/18] cxl: Add Set Feature command support for user submission shiju.jose
2024-11-22 18:04 ` [PATCH v17 10/18] cxl: Add UUIDs for the CXL RAS features shiju.jose
2024-11-22 18:04 ` [PATCH v17 11/18] cxl/memfeature: Add CXL memory device patrol scrub control feature shiju.jose
2024-11-22 18:04 ` [PATCH v17 12/18] cxl/memfeature: Add CXL memory device ECS " shiju.jose
2024-11-22 18:04 ` [PATCH v17 13/18] ACPI:RAS2: Add ACPI RAS2 driver shiju.jose
2024-11-22 18:04 ` [PATCH v17 14/18] ras: mem: Add memory " shiju.jose
2024-11-22 18:04 ` [PATCH v17 15/18] EDAC: Add memory repair control feature shiju.jose
2024-11-22 18:04 ` [PATCH v17 16/18] cxl/mbox: Add support for PERFORM_MAINTENANCE mailbox command shiju.jose
2024-11-22 18:04 ` [PATCH v17 17/18] cxl/memfeature: Add CXL memory device soft PPR control feature shiju.jose
2024-11-22 18:04 ` [PATCH v17 18/18] cxl/memfeature: Add CXL memory device memory sparing " shiju.jose
2025-01-03 11:41 ` [PATCH v17 00/18] EDAC: Scrub: introduce generic EDAC RAS control feature driver + CXL/ACPI-RAS2 drivers Borislav Petkov
2025-01-03 13:02 ` Jonathan Cameron
2025-01-03 15:49 ` Dave Jiang
2025-01-03 18:32 ` Shiju Jose
2025-01-03 19:17 ` Shiju Jose [this message]
2025-01-03 19:26 ` Borislav Petkov
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=216de8e0176441e29a656865fc31d336@huawei.com \
--to=shiju.jose@huawei.com \
--cc=Jon.Grimm@amd.com \
--cc=Vilas.Sridharan@amd.com \
--cc=Yazen.Ghannam@amd.com \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=dferguson@amperecomputing.com \
--cc=duenwen@google.com \
--cc=erdemaktas@google.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-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=mchehab@kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=nifan.cxl@gmail.com \
--cc=pgonda@google.com \
--cc=prime.zeng@hisilicon.com \
--cc=rafael@kernel.org \
--cc=rientjes@google.com \
--cc=roberto.sassu@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=wbs@os.amperecomputing.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