From: Nikolay Borisov <nik.borisov@suse.com>
To: Yazen Ghannam <yazen.ghannam@amd.com>,
x86@kernel.org, Tony Luck <tony.luck@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
Smita.KoralahalliChannabasappa@amd.com,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v4 08/22] x86/mce/amd: Put list_head in threshold_bank
Date: Fri, 27 Jun 2025 14:14:40 +0300 [thread overview]
Message-ID: <fda62d41-ad87-4e33-9662-11d397a26f7c@suse.com> (raw)
In-Reply-To: <68039ee2-5407-4bd4-9735-62674805eaad@suse.com>
On 6/25/25 19:52, Nikolay Borisov wrote:
>
>
> On 6/24/25 17:16, Yazen Ghannam wrote:
>> The threshold_bank structure is a container for one or more
>> threshold_block structures. Currently, the container has a single
>> pointer to the 'first' threshold_block structure which then has a linked
>> list of the remaining threshold_block structures.
>>
>> This results in an extra level of indirection where the 'first' block is
>> checked before iterating over the remaining blocks.
>>
>> Remove the indirection by including the head of the block list in the
>> threshold_bank structure which already acts as a container for all the
>> bank's thresholding blocks.
>>
>> Reviewed-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
>> Tested-by: Tony Luck <tony.luck@intel.com>
>> Reviewed-by: Tony Luck <tony.luck@intel.com>
>> Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
>> ---
>>
>> Notes:
>> Link:
>> https://lore.kernel.org/r/20250415-wip-mca-updates-
>> v3-4-8ffd9eb4aa56@amd.com
>> v3->v4:
>> * No change.
>> v2->v3:
>> * Added tags from Qiuxu and Tony.
>> v1->v2:
>> * New in v2.
>>
>> arch/x86/kernel/cpu/mce/amd.c | 43 +++++++++++
>> +-------------------------------
>> 1 file changed, 12 insertions(+), 31 deletions(-)
>>
>> diff --git a/arch/x86/kernel/cpu/mce/amd.c b/arch/x86/kernel/cpu/mce/
>> amd.c
>> index 0ffbee329a8c..5d351ec863cd 100644
>> --- a/arch/x86/kernel/cpu/mce/amd.c
>> +++ b/arch/x86/kernel/cpu/mce/amd.c
>> @@ -241,7 +241,8 @@ struct threshold_block {
>> struct threshold_bank {
>> struct kobject *kobj;
>> - struct threshold_block *blocks;
>> + /* List of threshold blocks within this MCA bank. */
>> + struct list_head miscj;
>> };
>> static DEFINE_PER_CPU(struct threshold_bank **, threshold_banks);
>> @@ -900,9 +901,9 @@ static void log_and_reset_block(struct
>> threshold_block *block)
>> */
>> static void amd_threshold_interrupt(void)
>> {
>> - struct threshold_block *first_block = NULL, *block = NULL, *tmp =
>> NULL;
>> - struct threshold_bank **bp = this_cpu_read(threshold_banks);
>> + struct threshold_bank **bp = this_cpu_read(threshold_banks),
>> *thr_bank;
>> unsigned int bank, cpu = smp_processor_id();
>> + struct threshold_block *block, *tmp;
>> /*
>> * Validate that the threshold bank has been initialized
>> already. The
>> @@ -916,16 +917,11 @@ static void amd_threshold_interrupt(void)
>> if (!(per_cpu(bank_map, cpu) & BIT_ULL(bank)))
>> continue;
>
> <slight off topic>
>
> nit: I wonder if instead of using per_cpu and manual bit testing can't a
> direct
> call to x86_this_cpu_test_bit be a better solution. The assembly looks
> like:
>
> [OLD]
>
> xorl %r14d, %r14d # ivtmp.245
> movq %rax, 8(%rsp) # cpu, %sfp
> # arch/x86/kernel/cpu/mce/amd.c:917: if (!(per_cpu(bank_map, cpu)
> & BIT_ULL(bank)))
> movq $bank_map, %rax #, __ptr
> movq %rax, (%rsp) # __ptr, %sfp
> .L236:
> movq 8(%rsp), %rax # %sfp, cpu
> # arch/x86/kernel/cpu/mce/amd.c:917: if (!(per_cpu(bank_map, cpu)
> & BIT_ULL(bank)))
> movq (%rsp), %rsi # %sfp, __ptr
> # arch/x86/kernel/cpu/mce/amd.c:917: if (!(per_cpu(bank_map, cpu)
> & BIT_ULL(bank)))
> movq __per_cpu_offset(,%rax,8), %rax # __per_cpu_offset[cpu_23],
> __per_cpu_offset[cpu_23]
> # arch/x86/kernel/cpu/mce/amd.c:917: if (!(per_cpu(bank_map, cpu)
> & BIT_ULL(bank)))
> movq (%rax,%rsi), %rax
> # arch/x86/kernel/cpu/mce/amd.c:917: if (!(per_cpu(bank_map, cpu)
> & BIT_ULL(bank)))
> btq %r14, %rax
>
> [NEW]
>
> xorl %r15d, %r15d # ivtmp.246
> .L236:
> # 917 "arch/x86/kernel/cpu/mce/amd.c" 1
> btl %r15d, %gs:bank_map(%rip) # ivtmp.246, *_9
>
>
> That way you end up with a single btl (but I guess a version that uses
> btq should be added as well)
> inside the loop rather than a bunch of instructions moving data around
> for per_cpu.
>
> Alternatively, since this is running in interrupt context can't you use
> directly this_cpu_read(bank_map) and eliminate the smp_processor_id
> invocation?
Actually the total number of banks are at most 128 as per the layout of
MCG_CAP register, so using btl is fine. Also I'm not sure why the
original code uses BIT_ULL vs just BIT since we can't have a 64bit value.
>
> </slight off topic>
>
>
> <snip>
>
next prev parent reply other threads:[~2025-06-27 11:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 14:15 [PATCH v4 00/22] AMD MCA interrupts rework Yazen Ghannam
2025-06-24 14:15 ` [PATCH v4 01/22] x86/mce: Don't remove sysfs if thresholding sysfs init fails Yazen Ghannam
2025-06-28 11:33 ` [tip: ras/urgent] " tip-bot2 for Yazen Ghannam
2025-06-24 14:15 ` [PATCH v4 02/22] x86/mce: Restore poll settings after storm subsides Yazen Ghannam
2025-06-25 13:22 ` Nikolay Borisov
2025-06-28 11:33 ` [tip: ras/urgent] x86/mce: Ensure user polling settings are honored when restarting timer tip-bot2 for Yazen Ghannam
2025-06-24 14:15 ` [PATCH v4 03/22] x86/mce/amd: Add default names for MCA banks and blocks Yazen Ghannam
2025-06-28 11:33 ` [tip: ras/urgent] " tip-bot2 for Yazen Ghannam
2025-06-24 14:15 ` [PATCH v4 04/22] x86/mce/amd: Fix threshold limit reset Yazen Ghannam
2025-06-28 11:33 ` [tip: ras/urgent] " tip-bot2 for Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 05/22] x86/mce/amd: Rename threshold restart function Yazen Ghannam
2025-09-05 11:40 ` [tip: ras/core] " tip-bot2 for Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 06/22] x86/mce/amd: Remove return value for mce_threshold_{create,remove}_device() Yazen Ghannam
2025-06-25 14:57 ` Nikolay Borisov
2025-09-05 11:40 ` [tip: ras/core] " tip-bot2 for Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 07/22] x86/mce/amd: Remove smca_banks_map Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 08/22] x86/mce/amd: Put list_head in threshold_bank Yazen Ghannam
2025-06-25 16:52 ` Nikolay Borisov
2025-06-27 11:14 ` Nikolay Borisov [this message]
2025-06-30 12:57 ` Yazen Ghannam
2025-08-25 13:59 ` Borislav Petkov
2025-09-05 11:40 ` [tip: ras/core] " tip-bot2 for Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 09/22] x86/mce: Cleanup bank processing on init Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 10/22] x86/mce: Remove __mcheck_cpu_init_early() Yazen Ghannam
2025-06-26 8:03 ` Nikolay Borisov
2025-06-30 12:58 ` Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 11/22] x86/mce: Define BSP-only init Yazen Ghannam
2025-06-25 11:04 ` Nikolay Borisov
2025-06-25 11:26 ` Borislav Petkov
2025-06-24 14:16 ` [PATCH v4 12/22] x86/mce: Define BSP-only SMCA init Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 13/22] x86/mce: Do 'UNKNOWN' vendor check early Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 14/22] x86/mce: Separate global and per-CPU quirks Yazen Ghannam
2025-06-27 11:02 ` Nikolay Borisov
2025-06-30 13:00 ` Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 15/22] x86/mce: Move machine_check_poll() status checks to helper functions Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 16/22] x86/mce: Unify AMD THR handler with MCA Polling Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 17/22] x86/mce: Unify AMD DFR " Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 18/22] x86/mce/amd: Support SMCA Corrected Error Interrupt Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 19/22] x86/mce/amd: Remove redundant reset_block() Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 20/22] x86/mce/amd: Define threshold restart function for banks Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 21/22] x86/mce: Handle AMD threshold interrupt storms Yazen Ghannam
2025-06-24 14:16 ` [PATCH v4 22/22] x86/mce: Save and use APEI corrected threshold limit Yazen Ghannam
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=fda62d41-ad87-4e33-9662-11d397a26f7c@suse.com \
--to=nik.borisov@suse.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.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
all inboxes | Powered by JetHome®