From: Gabriele Monaco <gmonaco@redhat.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: linux-kernel@vger.kernel.org, Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH v12 8/9] cpumask: Add initialiser CPUMASK_NULL to use cleanup helpers
Date: Mon, 22 Sep 2025 10:07:54 +0000 (UTC) [thread overview]
Message-ID: <e4035ff8-729e-4fc7-b40a-0775dada8811@redhat.com> (raw)
In-Reply-To: <aM1vcBuOSh8OV7mN@yury>
2025-09-19T14:58:18Z Yury Norov <yury.norov@gmail.com>:
>> When you create a non-initialized variable on stack, compiler does
>> nothing about it, except for adjusting an argument to brk() emitted in
>> the function prologue.
>>
>> In this case, non-initialized struct cpumask is already on stack, and
>> switching from
>>
>> struct cpumask mask[1];
>>
>> to
>>
>> struct cpumask mask[1] = {};
>>
>> is really a no-op.
>
> Alright... The above is correct for optimization levels > 0.
> With -O0, 2nd version really makes GCC to initialize the array.
>
> https://godbolt.org/z/e1zG4K7M8
>
> This is not relevant for the kernel because -O2 is our default
> optimization level (I'm not even sure that -O0 is buildable).
> But you may want to mention that in commit message.
Thanks for testing that!
Makes totally sense. Although if it's something really unreachable in the kernel it may not make too much sense to mention in the commit message.
Also I'm not planning on sending another version after V13 [1], so we may let it slide.
Thanks,
Gabriele
[1] - https://lore.kernel.org/lkml/20250917161958.178925-1-gmonaco@redhat.com
next prev parent reply other threads:[~2025-09-22 10:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 14:59 [PATCH v12 0/9] timers: Exclude isolated cpus from timer migration Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 1/9] timers/migration: Postpone online/offline callbacks registration to late initcall Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 2/9] timers: Rename tmigr 'online' bit to 'available' Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 3/9] timers: Add the available mask in timer migration Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 4/9] timers: Use scoped_guard when setting/clearing the tmigr available flag Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 5/9] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_exclusion_cpumasks() Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 6/9] sched/isolation: Force housekeeping if isolcpus and nohz_full don't leave any Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 7/9] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping Gabriele Monaco
2025-09-15 20:43 ` Waiman Long
2025-09-16 8:31 ` Chen Ridong
2025-09-15 14:59 ` [PATCH v12 8/9] cpumask: Add initialiser CPUMASK_NULL to use cleanup helpers Gabriele Monaco
2025-09-15 16:04 ` Yury Norov
2025-09-15 17:02 ` Gabriele Monaco
2025-09-15 18:35 ` Yury Norov
2025-09-16 11:27 ` Frederic Weisbecker
2025-09-17 7:51 ` Gabriele Monaco
2025-09-17 11:38 ` Yury Norov
2025-09-17 12:08 ` Gabriele Monaco
2025-09-17 12:34 ` Yury Norov
2025-09-19 14:58 ` Yury Norov
2025-09-22 10:07 ` Gabriele Monaco [this message]
2025-09-15 14:59 ` [PATCH v12 9/9] timers: Exclude isolated cpus from timer migration Gabriele Monaco
2025-09-15 20:51 ` John B. Wyatt IV
2025-09-16 5:29 ` Gabriele Monaco
2025-09-16 13:41 ` Frederic Weisbecker
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=e4035ff8-729e-4fc7-b40a-0775dada8811@redhat.com \
--to=gmonaco@redhat.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yury.norov@gmail.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®