From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
Subject: [linux-next:master 11569/15343] drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c:1931:32-50: opportunity for str_on_off(mes -> dbgext_active)
Date: Thu, 08 Oct 2026 15:49:38 +0200 [thread overview]
Message-ID: <202610081540.BPLUol7s-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Yongqiang Sun <Yongqiang.Sun@amd.com>
CC: Alex Deucher <alexander.deucher@amd.com>
CC: Shaoyun Liu <Shaoyun.Liu@amd.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: aac26bee2287c88af5be5a5ff96d783b19a28790
commit: a367f2657fd6bce9ad5eb23a04619ac449cc3685 [11569/15343] drm/amdgpu: add mes_dbgext core support
:::::: branch date: 4 hours ago
:::::: commit date: 7 days ago
config: x86_64-randconfig-2100-20261008 (https://download.01.org/0day-ci/archive/20261008/202610081540.BPLUol7s-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
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>
| Reported-by: Julia Lawall <julia.lawall@inria.fr>
| Closes: https://lore.kernel.org/r/202610081540.BPLUol7s-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c:1931:32-50: opportunity for str_on_off(mes -> dbgext_active)
vim +1931 drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c
b2662d4cc4ce2d shaoyunl 2023-11-23 1914
a367f2657fd6bc Yongqiang Sun 2026-09-18 1915 /*
a367f2657fd6bc Yongqiang Sun 2026-09-18 1916 * Runtime on/off switch for the MES firmware debug extension.
a367f2657fd6bc Yongqiang Sun 2026-09-18 1917 *
a367f2657fd6bc Yongqiang Sun 2026-09-18 1918 * cat <debugfs>/amdgpu_mes_dbgext -> current state / size / mode
a367f2657fd6bc Yongqiang Sun 2026-09-18 1919 * echo 1 > <debugfs>/amdgpu_mes_dbgext -> enable
a367f2657fd6bc Yongqiang Sun 2026-09-18 1920 * echo 0 > <debugfs>/amdgpu_mes_dbgext -> disable
a367f2657fd6bc Yongqiang Sun 2026-09-18 1921 *
a367f2657fd6bc Yongqiang Sun 2026-09-18 1922 * When enabled with no boot-time size (mes_dbgext_buffer_size=0) a default
a367f2657fd6bc Yongqiang Sun 2026-09-18 1923 * buffer size is used; the collection method still follows mes_dbgext_options.
a367f2657fd6bc Yongqiang Sun 2026-09-18 1924 */
a367f2657fd6bc Yongqiang Sun 2026-09-18 1925 static int amdgpu_debugfs_mes_dbgext_show(struct seq_file *m, void *unused)
a367f2657fd6bc Yongqiang Sun 2026-09-18 1926 {
a367f2657fd6bc Yongqiang Sun 2026-09-18 1927 struct amdgpu_device *adev = m->private;
a367f2657fd6bc Yongqiang Sun 2026-09-18 1928 struct amdgpu_mes *mes = &adev->mes;
a367f2657fd6bc Yongqiang Sun 2026-09-18 1929
a367f2657fd6bc Yongqiang Sun 2026-09-18 1930 mutex_lock(&mes->dbgext_lock);
a367f2657fd6bc Yongqiang Sun 2026-09-18 @1931 seq_printf(m, "state: %s\n", mes->dbgext_active ? "on" : "off");
a367f2657fd6bc Yongqiang Sun 2026-09-18 1932 seq_printf(m, "size: %u KB x %u xcc\n", mes->dbgext_log_size / SZ_1K,
a367f2657fd6bc Yongqiang Sun 2026-09-18 1933 mes->dbgext_num_xcc ? mes->dbgext_num_xcc : 1);
a367f2657fd6bc Yongqiang Sun 2026-09-18 1934 seq_printf(m, "mode: %s\n",
a367f2657fd6bc Yongqiang Sun 2026-09-18 1935 mes->dbgext_use_irq ? "interrupt" : "polling");
a367f2657fd6bc Yongqiang Sun 2026-09-18 1936 seq_printf(m, "options: 0x%llx\n", mes->dbgext_log_options);
a367f2657fd6bc Yongqiang Sun 2026-09-18 1937 mutex_unlock(&mes->dbgext_lock);
b2662d4cc4ce2d shaoyunl 2023-11-23 1938
a367f2657fd6bc Yongqiang Sun 2026-09-18 1939 return 0;
a367f2657fd6bc Yongqiang Sun 2026-09-18 1940 }
a367f2657fd6bc Yongqiang Sun 2026-09-18 1941
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-08 13:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202610081540.BPLUol7s-lkp@intel.com \
--to=lkp@intel.com \
--cc=julia.lawall@inria.fr \
--cc=oe-kbuild@lists.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.