[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250109091915.GAZ3-Uk3rkuh38cQyy@fat_crate.local>
Date: Thu, 9 Jan 2025 10:19:15 +0100
From: Borislav Petkov <bp@...en8.de>
To: shiju.jose@...wei.com
Cc: linux-edac@...r.kernel.org, linux-cxl@...r.kernel.org,
linux-acpi@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, tony.luck@...el.com,
rafael@...nel.org, lenb@...nel.org, mchehab@...nel.org,
dan.j.williams@...el.com, dave@...olabs.net,
jonathan.cameron@...wei.com, dave.jiang@...el.com,
alison.schofield@...el.com, vishal.l.verma@...el.com,
ira.weiny@...el.com, david@...hat.com, Vilas.Sridharan@....com,
leo.duran@....com, Yazen.Ghannam@....com, rientjes@...gle.com,
jiaqiyan@...gle.com, Jon.Grimm@....com, dave.hansen@...ux.intel.com,
naoya.horiguchi@....com, james.morse@....com, jthoughton@...gle.com,
somasundaram.a@....com, erdemaktas@...gle.com, pgonda@...gle.com,
duenwen@...gle.com, gthelen@...gle.com,
wschwartz@...erecomputing.com, dferguson@...erecomputing.com,
wbs@...amperecomputing.com, nifan.cxl@...il.com,
tanxiaofei@...wei.com, prime.zeng@...ilicon.com,
roberto.sassu@...wei.com, kangkang.shen@...urewei.com,
wanghuiqiang@...wei.com, linuxarm@...wei.com
Subject: Re: [PATCH v18 04/19] EDAC: Add memory repair control feature
On Mon, Jan 06, 2025 at 12:10:00PM +0000, shiju.jose@...wei.com wrote:
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/min_hpa
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/min_dpa
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/min_nibble_mask
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/min_bank_group
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/min_bank
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/min_rank
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/min_row
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/min_column
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/min_channel
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/min_sub_channel
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/max_hpa
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/max_dpa
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/max_nibble_mask
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/max_bank_group
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/max_bank
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/max_rank
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/max_row
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/max_column
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/max_channel
> +What: /sys/bus/edac/devices/<dev-name>/mem_repairX/max_sub_channel
So this is new. I don't remember seeing that when I looked at your patches
the last time.
Looks like you have all those attributes and now you've decided to add a min
and max for each one, in addition. And UI-wise it is a madness as there are
gazillion single-value files now.
"Attributes should be ASCII text files, preferably with only one value per
file. It is noted that it may not be efficient to contain only one value per
file, so it is socially acceptable to express an array of values of the same
type."
So you don't need those - you can simply express each attribute as a range:
echo "1:2" > /sys/bus/edac/devices/<dev-name>/mem_repairX/bank
or if you wanna scrub only one bank:
echo "1:1" > /sys/bus/edac/devices/<dev-name>/mem_repairX/bank
What is the use case of that thing?
Someone might find it useful so let's add it preemptively?
Pfff.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists