From: kernel test robot <lkp@intel.com>
To: Babu Moger <babu.moger@amd.com>,
corbet@lwn.net, tony.luck@intel.com, reinette.chatre@intel.com,
Dave.Martin@arm.com, james.morse@arm.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev, x86@kernel.org, hpa@zytor.com,
akpm@linux-foundation.org, paulmck@kernel.org,
rostedt@goodmis.org, thuth@redhat.com, ardb@kernel.org,
gregkh@linuxfoundation.org, seanjc@google.com,
thomas.lendacky@amd.com, pawan.kumar.gupta@linux.intel.com,
perry.yuan@amd.com, yosry.ahmed@linux.dev, kai.huang@intel.com,
xiaoyao.li@intel.com, peterz@infradead.org,
kan.liang@linux.intel.com, mario.limonciello@amd.com,
xin3.li@intel.com, sohil.mehta@intel.com
Subject: Re: [PATCH v6 6/8] fs/resctrl: Introduce interface to display io_alloc CBMs
Date: Fri, 13 Jun 2025 12:28:54 +0800 [thread overview]
Message-ID: <202506131254.KDDf1FdT-lkp@intel.com> (raw)
In-Reply-To: <16cebf7069e11e07c0d9e343aa72363325befafd.1749677012.git.babu.moger@amd.com>
Hi Babu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on brauner-vfs/vfs.all]
[also build test WARNING on linus/master v6.16-rc1 next-20250612]
[cannot apply to tip/x86/core aegl/next]
[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/Babu-Moger/x86-cpufeatures-Add-support-for-L3-Smart-Data-Cache-Injection-Allocation-Enforcement/20250612-053050
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/16cebf7069e11e07c0d9e343aa72363325befafd.1749677012.git.babu.moger%40amd.com
patch subject: [PATCH v6 6/8] fs/resctrl: Introduce interface to display io_alloc CBMs
config: x86_64-randconfig-r071-20250612 (https://download.01.org/0day-ci/archive/20250613/202506131254.KDDf1FdT-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
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/202506131254.KDDf1FdT-lkp@intel.com/
New smatch warnings:
fs/resctrl/rdtgroup.c:2026 resctrl_io_alloc_cbm_show() warn: unsigned 'io_alloc_closid' is never less than zero.
fs/resctrl/rdtgroup.c:2026 resctrl_io_alloc_cbm_show() warn: error code type promoted to positive: 'io_alloc_closid'
Old smatch warnings:
fs/resctrl/rdtgroup.c:1961 resctrl_io_alloc_write() warn: unsigned 'io_alloc_closid' is never less than zero.
fs/resctrl/rdtgroup.c:1961 resctrl_io_alloc_write() warn: error code type promoted to positive: 'io_alloc_closid'
vim +/io_alloc_closid +2026 fs/resctrl/rdtgroup.c
1999
2000 static int resctrl_io_alloc_cbm_show(struct kernfs_open_file *of,
2001 struct seq_file *seq, void *v)
2002 {
2003 struct resctrl_schema *s = rdt_kn_parent_priv(of->kn);
2004 struct rdt_resource *r = s->res;
2005 u32 io_alloc_closid;
2006 int ret = 0;
2007
2008 cpus_read_lock();
2009 mutex_lock(&rdtgroup_mutex);
2010
2011 rdt_last_cmd_clear();
2012
2013 if (!r->cache.io_alloc_capable) {
2014 rdt_last_cmd_puts("io_alloc feature is not supported on the resource\n");
2015 ret = -ENODEV;
2016 goto cbm_show_out;
2017 }
2018
2019 if (!resctrl_arch_get_io_alloc_enabled(r)) {
2020 rdt_last_cmd_puts("io_alloc feature is not enabled\n");
2021 ret = -EINVAL;
2022 goto cbm_show_out;
2023 }
2024
2025 io_alloc_closid = resctrl_io_alloc_closid_get(r);
> 2026 if (io_alloc_closid < 0) {
2027 rdt_last_cmd_puts("Max CLOSID to support io_alloc is not available\n");
2028 ret = -EINVAL;
2029 goto cbm_show_out;
2030 }
2031
2032 show_doms(seq, resctrl_schema_io_alloc(s), NULL, io_alloc_closid);
2033
2034 cbm_show_out:
2035 mutex_unlock(&rdtgroup_mutex);
2036 cpus_read_unlock();
2037 return ret;
2038 }
2039
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-13 4:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 21:23 [PATCH v6 0/8] x86/resctrl: Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Babu Moger
2025-06-11 21:23 ` [PATCH v6 1/8] x86/cpufeatures: Add support for L3 Smart Data Cache Injection Allocation Enforcement Babu Moger
2025-06-11 21:23 ` [PATCH v6 2/8] x86/resctrl: Add SDCIAE feature in the command line options Babu Moger
2025-06-11 21:23 ` [PATCH v6 3/8] x86/resctrl: Detect io_alloc feature Babu Moger
2025-06-18 3:45 ` Reinette Chatre
2025-06-18 19:27 ` Moger, Babu
2025-06-11 21:23 ` [PATCH v6 4/8] x86/resctrl: Implement "io_alloc" enable/disable handlers Babu Moger
2025-06-18 3:51 ` Reinette Chatre
2025-06-18 19:27 ` Moger, Babu
2025-06-18 20:32 ` Reinette Chatre
2025-06-18 21:57 ` Moger, Babu
2025-06-11 21:23 ` [PATCH v6 5/8] fs/resctrl: Add user interface to enable/disable io_alloc feature Babu Moger
2025-06-13 1:42 ` kernel test robot
2025-06-13 4:18 ` kernel test robot
2025-06-18 3:59 ` Reinette Chatre
2025-06-19 18:41 ` Moger, Babu
2025-06-20 15:53 ` Reinette Chatre
2025-06-20 21:57 ` Moger, Babu
2025-06-11 21:23 ` [PATCH v6 6/8] fs/resctrl: Introduce interface to display io_alloc CBMs Babu Moger
2025-06-13 4:28 ` kernel test robot [this message]
2025-06-18 4:01 ` Reinette Chatre
2025-06-20 21:57 ` Moger, Babu
2025-06-11 21:23 ` [PATCH v6 7/8] fs/resctrl: Modify rdt_parse_data to pass mode and CLOSID Babu Moger
2025-06-18 4:03 ` Reinette Chatre
2025-06-20 21:58 ` Moger, Babu
2025-06-11 21:23 ` [PATCH v6 8/8] fs/resctrl: Introduce interface to modify io_alloc Capacity Bit Masks Babu Moger
2025-06-13 7:04 ` kernel test robot
2025-06-16 14:51 ` Moger, Babu
2025-06-18 4:03 ` Reinette Chatre
2025-06-20 21:58 ` Moger, Babu
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=202506131254.KDDf1FdT-lkp@intel.com \
--to=lkp@intel.com \
--cc=Dave.Martin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=kai.huang@intel.com \
--cc=kan.liang@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=perry.yuan@amd.com \
--cc=peterz@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=thuth@redhat.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=xin3.li@intel.com \
--cc=yosry.ahmed@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.