mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maksim Davydov <davydov-max@yandex-team.ru>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, davydov-max@yandex-team.ru,
	den-plotnikov@yandex-team.ru, dave.hansen@linux.intel.com,
	tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	gpiccoli@igalia.com
Subject: Re: [PATCH v2] x86/split_lock: fix delayed detection enabling
Date: Fri, 3 May 2024 08:28:05 +0800	[thread overview]
Message-ID: <202405030838.XyIfnymG-lkp@intel.com> (raw)
In-Reply-To: <20240502102731.84429-1-davydov-max@yandex-team.ru>

Hi Maksim,

kernel test robot noticed the following build warnings:

[auto build test WARNING on tip/x86/core]
[also build test WARNING on tip/master linus/master v6.9-rc6 next-20240502]
[cannot apply to tip/auto-latest]
[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/Maksim-Davydov/x86-split_lock-fix-delayed-detection-enabling/20240502-183110
base:   tip/x86/core
patch link:    https://lore.kernel.org/r/20240502102731.84429-1-davydov-max%40yandex-team.ru
patch subject: [PATCH v2] x86/split_lock: fix delayed detection enabling
config: i386-buildonly-randconfig-005-20240503 (https://download.01.org/0day-ci/archive/20240503/202405030838.XyIfnymG-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240503/202405030838.XyIfnymG-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/202405030838.XyIfnymG-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> arch/x86/kernel/cpu/intel.c:1113:13: warning: '__split_lock_reenable' defined but not used [-Wunused-function]
    1113 | static void __split_lock_reenable(struct work_struct *work)
         |             ^~~~~~~~~~~~~~~~~~~~~


vim +/__split_lock_reenable +1113 arch/x86/kernel/cpu/intel.c

727209376f4998 Guilherme G. Piccoli 2022-10-24  1112  
727209376f4998 Guilherme G. Piccoli 2022-10-24 @1113  static void __split_lock_reenable(struct work_struct *work)
727209376f4998 Guilherme G. Piccoli 2022-10-24  1114  {
727209376f4998 Guilherme G. Piccoli 2022-10-24  1115  	sld_update_msr(true);
727209376f4998 Guilherme G. Piccoli 2022-10-24  1116  }
73f2dbc05507dd Maksim Davydov       2024-05-02  1117  /*
73f2dbc05507dd Maksim Davydov       2024-05-02  1118   * In order for each CPU to schedule itself delayed work independently of the
73f2dbc05507dd Maksim Davydov       2024-05-02  1119   * others, delayed work struct should be per-CPU. This is not required when
73f2dbc05507dd Maksim Davydov       2024-05-02  1120   * sysctl_sld_mitigate is enabled because of the semaphore, that limits
73f2dbc05507dd Maksim Davydov       2024-05-02  1121   * the number of simultaneously scheduled delayed works to 1.
73f2dbc05507dd Maksim Davydov       2024-05-02  1122   */
73f2dbc05507dd Maksim Davydov       2024-05-02  1123  static DEFINE_PER_CPU(struct delayed_work, sl_reenable);
73f2dbc05507dd Maksim Davydov       2024-05-02  1124  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      reply	other threads:[~2024-05-03  0:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 10:27 Maksim Davydov
2024-05-03  0:28 ` kernel test robot [this message]

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=202405030838.XyIfnymG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=davydov-max@yandex-team.ru \
    --cc=den-plotnikov@yandex-team.ru \
    --cc=gpiccoli@igalia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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®