From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6-desktop 15/67] mm/swap.c:722:9: error: implicit declaration of function 'folio_update_drain'; did you mean 'folio_activate_drain'?
Date: Sun, 17 Nov 2024 01:46:45 +0800 [thread overview]
Message-ID: <202411170103.PPdWSFlT-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android15-6.6-desktop
head: e2b6daceb83c9b9ae90fca4b78fc265484ded662
commit: 502d91a72b9c5bef5d3ae1b7b2b3a9901a8a4e2f [15/67] CHROMIUM: mm/mglru: slow down promotion through page tables
config: arm-vf610m4_defconfig (https://download.01.org/0day-ci/archive/20241117/202411170103.PPdWSFlT-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241117/202411170103.PPdWSFlT-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/202411170103.PPdWSFlT-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/swap.c: In function 'lru_add_drain_cpu':
>> mm/swap.c:722:9: error: implicit declaration of function 'folio_update_drain'; did you mean 'folio_activate_drain'? [-Wimplicit-function-declaration]
722 | folio_update_drain(cpu);
| ^~~~~~~~~~~~~~~~~~
| folio_activate_drain
vim +722 mm/swap.c
685
686 /*
687 * Drain pages out of the cpu's folio_batch.
688 * Either "cpu" is the current CPU, and preemption has already been
689 * disabled; or "cpu" is being hot-unplugged, and is already dead.
690 */
691 void lru_add_drain_cpu(int cpu)
692 {
693 struct cpu_fbatches *fbatches = &per_cpu(cpu_fbatches, cpu);
694 struct folio_batch *fbatch = &fbatches->lru_add;
695
696 if (folio_batch_count(fbatch))
697 folio_batch_move_lru(fbatch, lru_add_fn);
698
699 fbatch = &per_cpu(lru_rotate.fbatch, cpu);
700 /* Disabling interrupts below acts as a compiler barrier. */
701 if (data_race(folio_batch_count(fbatch))) {
702 unsigned long flags;
703
704 /* No harm done if a racing interrupt already did this */
705 local_lock_irqsave(&lru_rotate.lock, flags);
706 folio_batch_move_lru(fbatch, lru_move_tail_fn);
707 local_unlock_irqrestore(&lru_rotate.lock, flags);
708 }
709
710 fbatch = &fbatches->lru_deactivate_file;
711 if (folio_batch_count(fbatch))
712 folio_batch_move_lru(fbatch, lru_deactivate_file_fn);
713
714 fbatch = &fbatches->lru_deactivate;
715 if (folio_batch_count(fbatch))
716 folio_batch_move_lru(fbatch, lru_deactivate_fn);
717
718 fbatch = &fbatches->lru_lazyfree;
719 if (folio_batch_count(fbatch))
720 folio_batch_move_lru(fbatch, lru_lazyfree_fn);
721
> 722 folio_update_drain(cpu);
723 }
724
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-16 17:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202411170103.PPdWSFlT-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.