From: Peter Xu <peterx@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kbuild-all@lists.01.org, Andrea Arcangeli <aarcange@redhat.com>,
Andi Kleen <andi.kleen@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Hugh Dickins <hughd@google.com>,
Huang Ying <ying.huang@intel.com>,
Nadav Amit <nadav.amit@gmail.com>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH 2/2] mm: Remember young bit for page migrations
Date: Wed, 3 Aug 2022 17:47:44 -0400 [thread overview]
Message-ID: <YurtAFQ9xfZ7KfOF@xz-m1.local> (raw)
In-Reply-To: <202208032031.PVcMB0Hr-lkp@intel.com>
On Wed, Aug 03, 2022 at 08:21:43PM +0800, kernel test robot wrote:
> Hi Peter,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on akpm-mm/mm-everything]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Peter-Xu/mm-Remember-young-bit-for-migration-entries/20220803-092311
> base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
> config: openrisc-randconfig-r016-20220803 (https://download.01.org/0day-ci/archive/20220803/202208032031.PVcMB0Hr-lkp@intel.com/config)
> compiler: or1k-linux-gcc (GCC) 12.1.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://github.com/intel-lab-lkp/linux/commit/2fca6cb25745d1404fc34e0ec2ea89b6195a8c27
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Peter-Xu/mm-Remember-young-bit-for-migration-entries/20220803-092311
> git checkout 2fca6cb25745d1404fc34e0ec2ea89b6195a8c27
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=openrisc SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> or1k-linux-ld: mm/rmap.o: in function `migration_entry_supports_young':
> >> include/linux/swapops.h:288: undefined reference to `max_swapfile_size'
> include/linux/swapops.h:288:(.text+0x31a0): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `max_swapfile_size'
> or1k-linux-ld: mm/migrate.o: in function `migration_entry_supports_young':
> >> include/linux/swapops.h:288: undefined reference to `max_swapfile_size'
> include/linux/swapops.h:288:(.text+0x158): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `max_swapfile_size'
Hmm, a bit surprised to know swapops.h will be used without CONFIG_SWAP..
I'll squash this in the next version (if not going via a page flag based
approach):
diff --git a/include/linux/swapops.h b/include/linux/swapops.h
index 9ddede3790a4..d689f59479c3 100644
--- a/include/linux/swapops.h
+++ b/include/linux/swapops.h
@@ -285,7 +285,11 @@ static inline bool migration_entry_supports_young(void)
* entry has the offset larger than storing the PFN value, then it
* means there's extra bit(s) where we can store the young bit.
*/
+#ifdef CONFIG_SWAP
return max_swapfile_size() > SWP_MIG_YOUNG_BIT;
+#else
+ return false;
+#endif
}
static inline swp_entry_t make_migration_entry_young(swp_entry_t entry)
--
Peter Xu
next prev parent reply other threads:[~2022-08-03 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 1:21 [PATCH 0/2] mm: Remember young bit for migration entries Peter Xu
2022-08-03 1:21 ` [PATCH 1/2] mm/swap: Add swp_offset_pfn() to fetch PFN from swap entry Peter Xu
2022-08-03 1:21 ` [PATCH 2/2] mm: Remember young bit for page migrations Peter Xu
2022-08-03 7:42 ` Nadav Amit
2022-08-03 16:45 ` Peter Xu
2022-08-04 6:42 ` Nadav Amit
2022-08-04 17:07 ` Peter Xu
2022-08-04 17:16 ` Nadav Amit
2022-08-03 12:21 ` kernel test robot
2022-08-03 21:47 ` Peter Xu [this message]
2022-08-03 13:53 ` 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=YurtAFQ9xfZ7KfOF@xz-m1.local \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=kbuild-all@lists.01.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=nadav.amit@gmail.com \
--cc=vbabka@suse.cz \
--cc=ying.huang@intel.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