public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.vnet.ibm.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, dietmar.eggemann@arm.com,
	vschneid@redhat.com, linux-kernel@vger.kernel.org,
	ionela.voinescu@arm.com, quentin.perret@arm.com,
	srikar@linux.vnet.ibm.com, mgorman@techsingularity.net,
	mingo@kernel.org, pierre.gondois@arm.com, yu.c.chen@intel.com,
	tim.c.chen@linux.intel.com, mingo@redhat.com,
	vincent.guittot@linaro.org
Subject: Re: [PATCH v3] sched/topology: remove sysctl_sched_energy_aware depending on the architecture
Date: Thu, 14 Sep 2023 23:29:31 +0530	[thread overview]
Message-ID: <46ef47cf-4aea-65ed-09e1-ad8562b4e693@linux.vnet.ibm.com> (raw)
In-Reply-To: <202309140704.YiAtZ0yy-lkp@intel.com>



On 9/14/23 5:31 AM, kernel test robot wrote:
> Hi Shrikanth,
> 
> kernel test robot noticed the following build warnings:
> 
> [auto build test WARNING on tip/sched/core]
> [also build test WARNING on linus/master v6.6-rc1 next-20230913]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Shrikanth-Hegde/sched-topology-remove-sysctl_sched_energy_aware-depending-on-the-architecture/20230913-195055
> base:   tip/sched/core
> patch link:    https://lore.kernel.org/r/20230913114807.665094-1-sshegde%40linux.vnet.ibm.com
> patch subject: [PATCH v3] sched/topology: remove sysctl_sched_energy_aware depending on the architecture
> config: x86_64-buildonly-randconfig-003-20230914 (https://download.01.org/0day-ci/archive/20230914/202309140704.YiAtZ0yy-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230914/202309140704.YiAtZ0yy-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202309140704.YiAtZ0yy-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>    In file included from kernel/sched/build_utility.c:89:
>>> kernel/sched/topology.c:212:33: warning: 'sysctl_eas_header' defined but not used [-Wunused-variable]
>      212 | static struct ctl_table_header *sysctl_eas_header;
>          |                                 ^~~~~~~~~~~~~~~~~
> 

Hi. 

Thanks for pointing it out. This could be done by setting CONFIG_PROC_SYSCTL=n
have refactored the code and it likely make it simpler. will send out v4. 


> 
> vim +/sysctl_eas_header +212 kernel/sched/topology.c
> 
>    208	
>    209	#if defined(CONFIG_ENERGY_MODEL) && defined(CONFIG_CPU_FREQ_GOV_SCHEDUTIL)
>    210	DEFINE_STATIC_KEY_FALSE(sched_energy_present);
>    211	static unsigned int sysctl_sched_energy_aware;
>  > 212	static struct ctl_table_header *sysctl_eas_header;
>    213	static DEFINE_MUTEX(sched_energy_mutex);
>    214	static bool sched_energy_update;
>    215	static bool is_sysctl_eas_changing;
>    216	
> 

  reply	other threads:[~2023-09-14 18:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 11:48 [PATCH v3] sched/topology: remove sysctl_sched_energy_aware depending on the architecture Shrikanth Hegde
2023-09-14  0:01 ` kernel test robot
2023-09-14 17:59   ` Shrikanth Hegde [this message]
2023-09-14 16:21 ` Valentin Schneider
2023-09-14 17:56   ` Shrikanth Hegde
2023-09-15 12:00     ` Valentin Schneider
2023-09-15 13:35       ` Pierre Gondois
2023-09-18 12:21         ` Valentin Schneider
2023-09-15 18:10       ` Shrikanth Hegde
2023-09-18 12:22         ` Valentin Schneider
2023-09-18 17:39           ` Shrikanth Hegde
2023-09-22 14:44           ` Pierre Gondois
2023-09-22 21:02             ` Shrikanth Hegde
2023-09-20 17:47       ` Shrikanth Hegde
2023-09-18 12:00 ` Pierre Gondois
2023-09-18 12:57   ` Phil Auld

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=46ef47cf-4aea-65ed-09e1-ad8562b4e693@linux.vnet.ibm.com \
    --to=sshegde@linux.vnet.ibm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=ionela.voinescu@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mgorman@techsingularity.net \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pierre.gondois@arm.com \
    --cc=quentin.perret@arm.com \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=yu.c.chen@intel.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