From: kernel test robot <lkp@intel.com>
To: Jiri Bohac <jbohac@suse.cz>, Baoquan He <bhe@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>, Dave Young <dyoung@redhat.com>,
kexec@lists.infradead.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
mhocko@suse.cz
Subject: Re: [PATCH 1/4] kdump: add crashkernel cma suffix
Date: Sat, 25 Nov 2023 15:24:22 +0800 [thread overview]
Message-ID: <202311251303.71yrbT6l-lkp@intel.com> (raw)
In-Reply-To: <ZWEAPXiCCgAf1WrY@dwarf.suse.cz>
Hi Jiri,
kernel test robot noticed the following build warnings:
[auto build test WARNING on powerpc/next]
[also build test WARNING on powerpc/fixes s390/features linus/master v6.7-rc2 next-20231124]
[cannot apply to tip/x86/core arm64/for-next/core]
[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/Jiri-Bohac/kdump-implement-reserve_crashkernel_cma/20231125-082724
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
patch link: https://lore.kernel.org/r/ZWEAPXiCCgAf1WrY%40dwarf.suse.cz
patch subject: [PATCH 1/4] kdump: add crashkernel cma suffix
config: alpha-randconfig-r081-20231125 (https://download.01.org/0day-ci/archive/20231125/202311251303.71yrbT6l-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231125/202311251303.71yrbT6l-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/202311251303.71yrbT6l-lkp@intel.com/
All warnings (new ones prefixed by >>):
kernel/crash_core.c: In function 'parse_crashkernel':
>> kernel/crash_core.c:319:28: warning: unused variable 'cma_base' [-Wunused-variable]
319 | unsigned long long cma_base;
| ^~~~~~~~
vim +/cma_base +319 kernel/crash_core.c
302
303 /*
304 * That function is the entry point for command line parsing and should be
305 * called from the arch-specific code.
306 *
307 * If crashkernel=,high|low is supported on architecture, non-NULL values
308 * should be passed to parameters 'low_size' and 'high'.
309 */
310 int __init parse_crashkernel(char *cmdline,
311 unsigned long long system_ram,
312 unsigned long long *crash_size,
313 unsigned long long *crash_base,
314 unsigned long long *low_size,
315 unsigned long long *cma_size,
316 bool *high)
317 {
318 int ret;
> 319 unsigned long long cma_base;
320
321 /* crashkernel=X[@offset] */
322 ret = __parse_crashkernel(cmdline, system_ram, crash_size,
323 crash_base, NULL);
324 #ifdef CONFIG_ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION
325 /*
326 * If non-NULL 'high' passed in and no normal crashkernel
327 * setting detected, try parsing crashkernel=,high|low.
328 */
329 if (high && ret == -ENOENT) {
330 ret = __parse_crashkernel(cmdline, 0, crash_size,
331 crash_base, suffix_tbl[SUFFIX_HIGH]);
332 if (ret || !*crash_size)
333 return -EINVAL;
334
335 /*
336 * crashkernel=Y,low can be specified or not, but invalid value
337 * is not allowed.
338 */
339 ret = __parse_crashkernel(cmdline, 0, low_size,
340 crash_base, suffix_tbl[SUFFIX_LOW]);
341 if (ret == -ENOENT) {
342 *low_size = DEFAULT_CRASH_KERNEL_LOW_SIZE;
343 ret = 0;
344 } else if (ret) {
345 return ret;
346 }
347
348 *high = true;
349 }
350
351 /*
352 * optional CMA reservation
353 * cma_base is ignored
354 */
355 if (cma_size)
356 __parse_crashkernel(cmdline, 0, cma_size,
357 &cma_base, suffix_tbl[SUFFIX_CMA]);
358 #endif
359 if (!*crash_size)
360 ret = -EINVAL;
361
362 return ret;
363 }
364
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-25 7:24 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 19:54 [PATCH 0/4] kdump: crashkernel reservation from CMA Jiri Bohac
2023-11-24 19:57 ` [PATCH 1/4] kdump: add crashkernel cma suffix Jiri Bohac
2023-11-25 7:24 ` kernel test robot [this message]
2023-11-24 19:58 ` [PATCH 2/4] kdump: implement reserve_crashkernel_cma Jiri Bohac
2023-11-24 19:58 ` [PATCH 3/4] kdump, x86: implement crashkernel CMA reservation Jiri Bohac
2023-11-24 19:58 ` [PATCH 4/4] kdump, documentation: describe craskernel " Jiri Bohac
2023-11-25 1:51 ` [PATCH 0/4] kdump: crashkernel reservation from CMA Tao Liu
2023-11-25 21:22 ` Jiri Bohac
2023-11-28 1:12 ` Tao Liu
2023-11-28 2:11 ` Baoquan He
2023-11-28 9:08 ` Michal Hocko
2023-11-29 7:57 ` Baoquan He
2023-11-29 9:25 ` Michal Hocko
2023-11-30 2:42 ` Baoquan He
2023-11-29 10:51 ` Jiri Bohac
2023-11-30 4:01 ` Baoquan He
2023-12-01 12:35 ` Jiri Bohac
2023-11-29 8:10 ` Baoquan He
2023-11-29 15:03 ` Donald Dutile
2023-11-30 3:00 ` Baoquan He
2023-11-30 10:16 ` Michal Hocko
2023-11-30 12:04 ` Baoquan He
2023-11-30 12:31 ` Baoquan He
2023-11-30 13:41 ` Michal Hocko
2023-12-01 11:33 ` Philipp Rudo
2023-12-01 11:55 ` Michal Hocko
2023-12-01 15:51 ` Philipp Rudo
2023-12-01 16:59 ` Michal Hocko
2023-12-06 11:08 ` Philipp Rudo
2023-12-06 11:23 ` David Hildenbrand
2023-12-06 13:49 ` Michal Hocko
2023-12-06 15:19 ` Michal Hocko
2023-12-07 4:23 ` Baoquan He
2023-12-07 8:55 ` Michal Hocko
2023-12-07 11:13 ` Philipp Rudo
2023-12-07 11:52 ` Michal Hocko
2023-12-08 1:55 ` Baoquan He
2023-12-08 10:04 ` Michal Hocko
2023-12-08 2:10 ` Baoquan He
2023-12-07 11:13 ` Philipp Rudo
2023-11-30 13:29 ` Michal Hocko
2023-11-30 13:33 ` Pingfan Liu
2023-11-30 13:43 ` Michal Hocko
2023-12-01 0:54 ` Pingfan Liu
2023-12-01 10:37 ` Michal Hocko
2023-11-28 2:07 ` Pingfan Liu
2023-11-28 8:58 ` Michal Hocko
2023-12-01 11:34 ` Philipp Rudo
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=202311251303.71yrbT6l-lkp@intel.com \
--to=lkp@intel.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=jbohac@suse.cz \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vgoyal@redhat.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