From: Mike Rapoport <rppt@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v13 4/8] x86: kdump: move reserve_crashkernel[_low]() into crash_core.c
Date: Thu, 12 Nov 2020 11:39:25 +0200 [thread overview]
Message-ID: <20201112093925.GM4758@kernel.org> (raw)
In-Reply-To: <c4ca44ea-bf1c-7bbe-4897-849316ecacf3@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 5287 bytes --]
On Thu, Nov 12, 2020 at 04:17:01PM +0800, chenzhou wrote:
> Hi all,
>
>
> On 2020/11/11 21:20, kernel test robot wrote:
> > Hi Chen,
> >
> > Thank you for the patch! Perhaps something to improve:
> >
> > [auto build test WARNING on tip/master]
> > [also build test WARNING on linus/master v5.10-rc3 next-20201111]
> > [cannot apply to arm64/for-next/core tip/x86/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]
> >
> > url: https://github.com/0day-ci/linux/commits/Chen-Zhou/support-reserving-crashkernel-above-4G-on-arm64-kdump/20201031-154154
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 6f72faf4a32303c8bdc6491186b79391e9cf0c7e
> > config: i386-randconfig-r024-20201110 (attached as .config)
> > compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
> > reproduce (this is a W=1 build):
> > # https://github.com/0day-ci/linux/commit/0384057e2a51e71f42a0e1cb9d37555f4f37874e
> > git remote add linux-review https://github.com/0day-ci/linux
> > git fetch --no-tags linux-review Chen-Zhou/support-reserving-crashkernel-above-4G-on-arm64-kdump/20201031-154154
> > git checkout 0384057e2a51e71f42a0e1cb9d37555f4f37874e
> > # save the attached .config to linux build tree
> > make W=1 ARCH=i386
> >
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <lkp@intel.com>
> >
> > All warnings (new ones prefixed by >>):
> >
> > In file included from arch/x86/kernel/setup.c:39:
> >>> arch/x86/include/asm/kexec.h:77: warning: "vmcore_elf_check_arch_cross" redefined
> > 77 | # define vmcore_elf_check_arch_cross(x) ((x)->e_machine == EM_X86_64)
> > |
> > In file included from arch/x86/kernel/setup.c:9:
> > include/linux/crash_dump.h:39: note: this is the location of the previous definition
> > 39 | #define vmcore_elf_check_arch_cross(x) 0
> > |
> The root cause is that some code under CONFIG_CRASH_CORE depend on CONFIG_KEXEC_CORE.
>
> Patch series "kexec/fadump: remove dependency with CONFIG_KEXEC and reuse crashkernel
> parameter for fadump" removes dependency with CONFIG_KEXEC for crashkernel parameter
> and vmcoreinfo related code.
> This patch series introduce CONFIG_CRASH_CORE and move code related to vmcoreinfo and
> parsing of crashkernel parameter under this config, allowing code reuse without dependency
> on CONFIG_KEXEC.
>
> But some functions and macros(in file asm/kexec.h) related with vmcoreinfo may also have
> this dependency on CONFIG_KEXEC/CONFIG_KEXEC_CORE.
>
> For example, for x86_32, the macro vmcore_elf_check_arch_cross, if CONFIG_KEXEC_CORE
> is disabled, vmcore_elf_check_arch_cross will always return 0. I think this is wrong.
> # git grep -w vmcore_elf_check_arch_cross
> arch/x86/include/asm/kexec.h:# define vmcore_elf_check_arch_cross(x) ((x)->e_machine == EM_X86_64)
> include/linux/crash_dump.h:#ifndef vmcore_elf_check_arch_cross
> include/linux/crash_dump.h:#define vmcore_elf_check_arch_cross(x) 0
> include/linux/crash_dump.h:#define vmcore_elf64_check_arch(x) (elf_check_arch(x) || vmcore_elf_check_arch_cross(x))
>
> I want to move these dependency functions and macros from asm/kexec.h to asm/crash_dump.h(new file),
> is my understanding right or any suggestions about this?
I'd simply move vmcore_elf_check_arch_cross() from
arch/x86/include/asm/kexec.h to arch/x86/include/elf.h.
The latter is already included in linux/crash_dump.h.
> Thanks,
> Chen Zhou
> > vim +/vmcore_elf_check_arch_cross +77 arch/x86/include/asm/kexec.h
> >
> > 3c233d1334ffc8 include/asm-x86/kexec.h Harvey Harrison 2008-01-30 75
> > 3c233d1334ffc8 include/asm-x86/kexec.h Harvey Harrison 2008-01-30 76 /* We can also handle crash dumps from 64 bit kernel. */
> > 3c233d1334ffc8 include/asm-x86/kexec.h Harvey Harrison 2008-01-30 @77 # define vmcore_elf_check_arch_cross(x) ((x)->e_machine == EM_X86_64)
> > 3c233d1334ffc8 include/asm-x86/kexec.h Harvey Harrison 2008-01-30 78 #else
> > 3c233d1334ffc8 include/asm-x86/kexec.h Harvey Harrison 2008-01-30 79 /* Maximum physical address we can use pages from */
> > 577af55d802d9f arch/x86/include/asm/kexec.h Yinghai Lu 2013-01-24 80 # define KEXEC_SOURCE_MEMORY_LIMIT (MAXMEM-1)
> > 3c233d1334ffc8 include/asm-x86/kexec.h Harvey Harrison 2008-01-30 81 /* Maximum address we can reach in physical address mode */
> > 577af55d802d9f arch/x86/include/asm/kexec.h Yinghai Lu 2013-01-24 82 # define KEXEC_DESTINATION_MEMORY_LIMIT (MAXMEM-1)
> > 3c233d1334ffc8 include/asm-x86/kexec.h Harvey Harrison 2008-01-30 83 /* Maximum address we can use for the control pages */
> > 577af55d802d9f arch/x86/include/asm/kexec.h Yinghai Lu 2013-01-24 84 # define KEXEC_CONTROL_MEMORY_LIMIT (MAXMEM-1)
> > 3c233d1334ffc8 include/asm-x86/kexec.h Harvey Harrison 2008-01-30 85
> >
> > ---
> > 0-DAY CI Kernel Test Service, Intel Corporation
> > https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2020-11-12 9:39 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 7:44 [PATCH v13 0/8] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` [PATCH v13 1/8] x86: kdump: replace the hard-coded alignment with macro CRASH_ALIGN Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-11-11 1:38 ` Baoquan He
2020-11-11 1:38 ` Baoquan He
2020-11-11 1:38 ` Baoquan He
2020-11-11 13:26 ` chenzhou
2020-11-11 13:26 ` chenzhou
2020-11-11 13:26 ` chenzhou
2020-11-12 7:58 ` Mike Rapoport
2020-11-12 7:58 ` Mike Rapoport
2020-11-12 7:58 ` Mike Rapoport
2020-11-12 8:12 ` chenzhou
2020-11-12 8:12 ` chenzhou
2020-11-12 8:12 ` chenzhou
2020-10-31 7:44 ` [PATCH v13 2/8] x86: kdump: make the lower bound of crash kernel reservation consistent Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` [PATCH v13 3/8] x86: kdump: use macro CRASH_ADDR_LOW_MAX in functions reserve_crashkernel() Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` [PATCH v13 4/8] x86: kdump: move reserve_crashkernel[_low]() into crash_core.c Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-11-11 13:20 ` kernel test robot
2020-11-12 8:17 ` chenzhou
2020-11-12 9:39 ` Mike Rapoport [this message]
2020-11-12 13:04 ` chenzhou
2020-11-12 8:11 ` Mike Rapoport
2020-11-12 8:11 ` Mike Rapoport
2020-11-12 8:11 ` Mike Rapoport
2020-11-12 13:01 ` chenzhou
2020-11-12 13:01 ` chenzhou
2020-11-12 13:01 ` chenzhou
2020-10-31 7:44 ` [PATCH v13 5/8] arm64: kdump: introduce some macroes for crash kernel reservation Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` [PATCH v13 6/8] arm64: kdump: reimplement crashkernel=X Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-11-11 1:59 ` Baoquan He
2020-11-11 1:59 ` Baoquan He
2020-11-11 1:59 ` Baoquan He
2020-11-11 13:27 ` chenzhou
2020-11-11 13:27 ` chenzhou
2020-11-11 13:27 ` chenzhou
2020-11-11 13:54 ` Baoquan He
2020-11-11 13:54 ` Baoquan He
2020-11-11 13:54 ` Baoquan He
2020-11-12 8:25 ` Mike Rapoport
2020-11-12 8:25 ` Mike Rapoport
2020-11-12 8:25 ` Mike Rapoport
2020-11-12 8:36 ` Baoquan He
2020-11-12 8:36 ` Baoquan He
2020-11-12 8:36 ` Baoquan He
2020-11-12 13:11 ` chenzhou
2020-11-12 13:11 ` chenzhou
2020-11-12 13:11 ` chenzhou
2020-10-31 7:44 ` [PATCH v13 7/8] arm64: kdump: add memory for devices by DT property linux, usable-memory-range Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` [PATCH v13 7/8] arm64: kdump: add memory for devices by DT property linux,usable-memory-range Chen Zhou
2020-10-31 7:44 ` [PATCH v13 8/8] kdump: update Documentation about crashkernel Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-10-31 7:44 ` Chen Zhou
2020-11-09 12:34 ` [PATCH v13 0/8] support reserving crashkernel above 4G on arm64 kdump chenzhou
2020-11-09 12:34 ` chenzhou
2020-11-09 12:34 ` chenzhou
2020-11-11 3:01 ` Baoquan He
2020-11-11 3:01 ` Baoquan He
2020-11-11 3:01 ` Baoquan He
2020-11-11 13:29 ` chenzhou
2020-11-11 13:29 ` chenzhou
2020-11-11 13:29 ` chenzhou
2020-11-11 19:41 ` Bhupesh SHARMA
2020-11-11 19:41 ` Bhupesh SHARMA
2020-11-11 19:41 ` Bhupesh SHARMA
-- strict thread matches above, loose matches on Subject: below --
2020-11-04 4:06 [PATCH v13 4/8] x86: kdump: move reserve_crashkernel[_low]() into crash_core.c kernel test robot
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=20201112093925.GM4758@kernel.org \
--to=rppt@kernel.org \
--cc=kbuild-all@lists.01.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 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.