From: kbuild test robot <lkp@intel.com>
To: Kairui Song <kasong@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de, bp@alien8.de, mingo@redhat.com,
hpa@zytor.com, jbohac@suse.cz, adobriyan@gmail.com,
akpm@linux-foundation.org, osandov@fb.com, bhsharma@redhat.com,
kasong@redhat.com, bhe@redhat.com, dyoung@redhat.com
Subject: Re: [PATCH 1/1] x86/gart/kcore: Exclude GART aperture from kcore
Date: Sun, 30 Dec 2018 03:43:57 +0800 [thread overview]
Message-ID: <201812300344.89taUcqA%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181221013812.22790-1-kasong@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
Hi Kairui,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.20 next-20181224]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Kairui-Song/x86-gart-kcore-Exclude-GART-aperture-from-kcore/20181221-132322
config: x86_64-randconfig-k2-12281339 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
arch/x86/kernel/aperture_64.o: In function `exclude_from_vmcore':
>> arch/x86/kernel/aperture_64.c:81: undefined reference to `register_mem_pfn_is_ram'
vim +81 arch/x86/kernel/aperture_64.c
75
76 static void exclude_from_vmcore(u64 aper_base, u32 aper_order)
77 {
78 aperture_pfn_start = aper_base >> PAGE_SHIFT;
79 aperture_page_count = (32 * 1024 * 1024) << aper_order >> PAGE_SHIFT;
80 WARN_ON(register_oldmem_pfn_is_ram(&gart_mem_pfn_is_ram));
> 81 WARN_ON(register_mem_pfn_is_ram(&gart_mem_pfn_is_ram));
82 }
83 #else
84 static void exclude_from_vmcore(u64 aper_base, u32 aper_order)
85 {
86 }
87 #endif
88
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32150 bytes --]
prev parent reply other threads:[~2018-12-29 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 1:38 Kairui Song
2018-12-21 14:56 ` Jiri Bohac
2018-12-29 19:43 ` kbuild 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=201812300344.89taUcqA%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bhsharma@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=jbohac@suse.cz \
--cc=kasong@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=osandov@fb.com \
--cc=tglx@linutronix.de \
/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®