linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Byungchul Park <byungchul@sk.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: oe-kbuild-all@lists.linux.dev, kernel_team@skhynix.com,
	akpm@linux-foundation.org, ying.huang@intel.com,
	namit@vmware.com, xhao@linux.alibaba.com,
	mgorman@techsingularity.net, hughd@google.com,
	willy@infradead.org, david@redhat.com, luto@kernel.org,
	tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com
Subject: Re: [v5 6/7] mm: Defer TLB flush by keeping both src and dst folios at migration
Date: Fri, 12 Jan 2024 06:12:40 +0800	[thread overview]
Message-ID: <202401120637.ZuSqfagi-lkp@intel.com> (raw)
In-Reply-To: <20240111060757.13563-7-byungchul@sk.com>

Hi Byungchul,

kernel test robot noticed the following build warnings:

[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on tip/sched/core tip/x86/core arm64/for-next/core tip/x86/mm linus/master v6.7 next-20240111]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Byungchul-Park/x86-tlb-Add-APIs-manipulating-tlb-batch-s-arch-data/20240111-141049
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20240111060757.13563-7-byungchul%40sk.com
patch subject: [v5 6/7] mm: Defer TLB flush by keeping both src and dst folios at migration
config: x86_64-randconfig-161-20240111 (https://download.01.org/0day-ci/archive/20240112/202401120637.ZuSqfagi-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240112/202401120637.ZuSqfagi-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/202401120637.ZuSqfagi-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> mm/migrate.c:152:6: warning: no previous prototype for 'migrc_flush_start' [-Wmissing-prototypes]
     152 | void migrc_flush_start(void)
         |      ^~~~~~~~~~~~~~~~~
>> mm/migrate.c:161:6: warning: no previous prototype for 'migrc_flush_end' [-Wmissing-prototypes]
     161 | void migrc_flush_end(struct arch_tlbflush_unmap_batch *arch)
         |      ^~~~~~~~~~~~~~~


vim +/migrc_flush_start +152 mm/migrate.c

   151	
 > 152	void migrc_flush_start(void)
   153	{
   154		unsigned long flags;
   155	
   156		spin_lock_irqsave(&migrc_lock, flags);
   157		migrc_flushing++;
   158		spin_unlock_irqrestore(&migrc_lock, flags);
   159	}
   160	
 > 161	void migrc_flush_end(struct arch_tlbflush_unmap_batch *arch)
   162	{
   163		LIST_HEAD(folios);
   164		struct folio *f, *f2;
   165		unsigned long flags;
   166	
   167		spin_lock_irqsave(&migrc_lock, flags);
   168		if (!arch_tlbbatch_done(&migrc_ubc.arch, arch)) {
   169			list_splice_init(&migrc_folios, &folios);
   170			migrc_ubc.flush_required = false;
   171			migrc_ubc.writable = false;
   172		}
   173		migrc_flushing--;
   174		spin_unlock_irqrestore(&migrc_lock, flags);
   175	
   176		list_for_each_entry_safe(f, f2, &folios, lru) {
   177			folio_put_small_nopcp(f);
   178			atomic_dec(&folio_zone(f)->migrc_pending_nr);
   179		}
   180	}
   181	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


  parent reply	other threads:[~2024-01-11 22:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  6:07 [v5 0/7] Reduce TLB flushes by 94% by improving folio migration Byungchul Park
2024-01-11  6:07 ` [v5 1/7] x86/tlb: Add APIs manipulating tlb batch's arch data Byungchul Park
2024-01-11  6:07 ` [v5 2/7] arm64: tlbflush: " Byungchul Park
2024-01-11  6:07 ` [v5 3/7] mm/rmap: Recognize read-only TLB entries during batched TLB flush Byungchul Park
2024-01-11  6:07 ` [v5 4/7] mm: Separate move/undo doing on folio list from migrate_pages_batch() Byungchul Park
2024-01-11 15:42   ` Matthew Wilcox
2024-01-15  2:08     ` Byungchul Park
2024-01-15  8:48       ` Byungchul Park
2024-01-11  6:07 ` [v5 5/7] mm: Add APIs to free a folio directly to the buddy bypassing pcp Byungchul Park
2024-01-11  6:07 ` [v5 6/7] mm: Defer TLB flush by keeping both src and dst folios at migration Byungchul Park
2024-01-11 18:44   ` kernel test robot
2024-01-11 19:58   ` kernel test robot
2024-01-11 22:12   ` kernel test robot [this message]
2024-01-11  6:07 ` [v5 7/7] mm: Pause migrc mechanism at high memory pressure Byungchul Park

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=202401120637.ZuSqfagi-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=byungchul@sk.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=kernel_team@skhynix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mingo@redhat.com \
    --cc=namit@vmware.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=willy@infradead.org \
    --cc=xhao@linux.alibaba.com \
    --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