From: Matthias Kaehlcke <mka@chromium.org>
To: Ingo Molnar <mingo@kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Shile Zhang <shile.zhang@nokia.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Nick Desaulniers <nick.desaulniers@gmail.com>,
Douglas Anderson <dianders@chromium.org>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [PATCH v2] sched/sysctl: Fix attributes of some extern declarations
Date: Tue, 31 Oct 2017 15:31:57 -0700 [thread overview]
Message-ID: <20171031223157.GF96615@google.com> (raw)
In-Reply-To: <20171031095758.wsgbrsdz7hzn5o2n@gmail.com>
El Tue, Oct 30, 2017 at 10:57:58AM +0100 Ingo Molnar ha dit:
> * Matthias Kaehlcke <mka@chromium.org> wrote:
>
> > The definition of sysctl_sched_migration_cost, sysctl_sched_nr_migrate
> > and sysctl_sched_time_avg includes the attribute const_debug. This
> > attribute is not part of the extern declaration of these variables in
> > include/linux/sched/sysctl.h, as a result clang generates warnings like
> > this:
> >
> > kernel/sched/sched.h:1618:33: warning: section attribute is specified on
> > redeclared variable [-Wsection]
> > extern const_debug unsigned int sysctl_sched_time_avg;
> > ^
> > ./include/linux/sched/sysctl.h:42:21: note: previous declaration is here
> > extern unsigned int sysctl_sched_time_avg;
> >
> > The header only declares the variables when CONFIG_SCHED_DEBUG is defined,
> > therefore it is not necessary to duplicate the definition of const_debug.
> > Instead we can use the attribute __read_mostly, which is the expansion of
> > const_debug when CONFIG_SCHED_DEBUG is set.
> >
> > Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> > Reviewed-by: Nick Desaulniers <nick.desaulniers@gmail.com>
> > ---
> > Changes in v2:
> > - removed pointless include of linux/static_key.h
> > - added Reviewed-by tag
> >
> > include/linux/sched/sysctl.h | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/include/linux/sched/sysctl.h b/include/linux/sched/sysctl.h
> > index 0f5ecd4d298e..d34c823f3d36 100644
> > --- a/include/linux/sched/sysctl.h
> > +++ b/include/linux/sched/sysctl.h
> > @@ -37,9 +37,9 @@ extern unsigned int sysctl_numa_balancing_scan_period_max;
> > extern unsigned int sysctl_numa_balancing_scan_size;
> >
> > #ifdef CONFIG_SCHED_DEBUG
> > -extern unsigned int sysctl_sched_migration_cost;
> > -extern unsigned int sysctl_sched_nr_migrate;
> > -extern unsigned int sysctl_sched_time_avg;
> > +extern __read_mostly unsigned int sysctl_sched_migration_cost;
> > +extern __read_mostly unsigned int sysctl_sched_nr_migrate;
> > +extern __read_mostly unsigned int sysctl_sched_time_avg;
>
> So I hate this change, because it pointlessly duplicates an attribute that should
> only matter at the definition site.
It's certainly not ideal, and then again essentially the same is done
in kernel/sched/sched.h, just that here the specific attribute is
hidden behind const_debug.
> The Clang warning:
>
> > kernel/sched/sched.h:1618:33: warning: section attribute is specified on
> > redeclared variable [-Wsection]
>
> suggests that the -Wsection warning can be turned off. The Clang build should
> probably do that.
That can definitely be done. I don't have a really strong opinion on
this, just wonder if the warning could be useful in other circumstances
to spot conflicting declarations. This instance looks like a somewhat
special case with the declarations in two header files and it might be
worth to pay the price of the pointlessly duplicate attribute to get a
useful warning in others.
Adding kbuild maintainer Masahiro Yamada to the thread, who tends to
be reluctant about disabling warnings globally.
next prev parent reply other threads:[~2017-10-31 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 18:08 Matthias Kaehlcke
2017-10-31 9:57 ` Ingo Molnar
2017-10-31 22:31 ` Matthias Kaehlcke [this message]
2017-11-01 4:33 ` Nick Desaulniers
2017-11-01 8:34 ` Ingo Molnar
2017-11-01 8:45 ` [tip:sched/core] " tip-bot for Matthias Kaehlcke
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=20171031223157.GF96615@google.com \
--to=mka@chromium.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nick.desaulniers@gmail.com \
--cc=peterz@infradead.org \
--cc=shile.zhang@nokia.com \
--cc=yamada.masahiro@socionext.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
Powered by JetHome