From: kbuild test robot <lkp@intel.com>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: kbuild-all@01.org, Timofey Titovets <nefelim4ag@gmail.com>,
linux-mm@kvack.org, Sioh Lee <solee@os.korea.ac.kr>,
Andrea Arcangeli <aarcange@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] ksm: replace jhash2 with faster hash
Date: Sun, 27 May 2018 04:25:18 +0800 [thread overview]
Message-ID: <201805270344.IExcwwSg%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180525011657.4qxrosmm3xjzo24w@xakep.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]
Hi Pavel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.17-rc6]
[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/Pavel-Tatashin/ksm-replace-jhash2-with-faster-hash/20180527-032512
base: git://git.cmpxchg.org/linux-mmotm.git master
config: i386-randconfig-x078-201821 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
mm/ksm.c: In function 'fasthash':
>> mm/ksm.c:338:15: error: implicit declaration of function 'xxhash'; did you mean 'jhash'? [-Werror=implicit-function-declaration]
return (u32)xxhash(input, length, 0);
^~~~~~
jhash
cc1: some warnings being treated as errors
vim +338 mm/ksm.c
331
332 static u32 fasthash(const void *input, size_t length)
333 {
334 if (static_branch_likely(&ksm_use_crc32c))
335 return crc32c(0, input, length);
336
337 if (static_branch_likely(&ksm_use_xxhash))
> 338 return (u32)xxhash(input, length, 0);
339
340 /* Is done only once on the first call of fasthash() */
341 fasthash_setup();
342
343 /* Now, that we know the hash alg., calculate checksum for zero page */
344 zero_checksum = fasthash(ZERO_PAGE(0), PAGE_SIZE);
345
346 return fasthash(input, length);
347 }
348
---
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: 27001 bytes --]
next prev parent reply other threads:[~2018-05-26 20:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 19:32 [PATCH V6 0/2 RESEND] KSM replace hash algo " Timofey Titovets
2018-04-18 19:32 ` [PATCH V6 1/2 RESEND] xxHash: create arch dependent 32/64-bit xxhash() Timofey Titovets
2018-04-18 19:32 ` [PATCH V6 2/2 RESEND] ksm: replace jhash2 with faster hash Timofey Titovets
2018-05-08 15:26 ` Claudio Imbrenda
2018-05-11 23:06 ` Timofey Titovets
2018-05-14 10:17 ` Claudio Imbrenda
2018-05-16 10:26 ` Timofey Titovets
2018-05-22 20:22 ` Pavel Tatashin
2018-05-23 13:45 ` Timofey Titovets
2018-05-23 14:24 ` Pavel Tatashin
2018-05-24 8:01 ` Timofey Titovets
2018-05-25 1:16 ` Pavel Tatashin
2018-05-26 20:25 ` kbuild test robot [this message]
2018-05-26 21:06 ` [PATCH] " kbuild test robot
2018-05-27 13:03 ` [PATCH V6 2/2 RESEND] " Mike Rapoport
2018-05-29 14:45 ` Pavel Tatashin
2018-06-07 8:58 ` Timofey Titovets
2018-06-07 11:52 ` Mike Rapoport
2018-06-08 1:29 ` Pavel Tatashin
2018-06-10 5:38 ` Mike Rapoport
2018-06-22 18:48 ` Pavel Tatashin
2018-06-25 8:48 ` Mike Rapoport
2018-09-13 10:35 ` Timofey Titovets
2018-09-13 18:01 ` Mike Rapoport
2018-09-13 18:10 ` Pasha Tatashin
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=201805270344.IExcwwSg%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aarcange@redhat.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nefelim4ag@gmail.com \
--cc=pasha.tatashin@oracle.com \
--cc=solee@os.korea.ac.kr \
/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