From: Oliver Sang <oliver.sang@intel.com>
To: Barry Song <21cnbao@gmail.com>
Cc: <lkp@intel.com>, <akpm@linux-foundation.org>,
<anshuman.khandual@arm.com>, <baolin.wang@linux.alibaba.com>,
<bp@alien8.de>, <catalin.marinas@arm.com>, <chrisl@kernel.org>,
<dave.hansen@linux.intel.com>, <david@redhat.com>,
<gshan@redhat.com>, <hpa@zytor.com>, <ioworker0@gmail.com>,
<kasong@tencent.com>, <kirill.shutemov@linux.intel.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<mark.rutland@arm.com>, <mingo@redhat.com>,
<oe-kbuild-all@lists.linux.dev>, <ryan.roberts@arm.com>,
<shahuang@redhat.com>, <tglx@linutronix.de>,
<v-songbaohua@oppo.com>, <wangkefeng.wang@huawei.com>,
<will@kernel.org>, <x86@kernel.org>, <ying.huang@intel.com>,
<yosryahmed@google.com>, <zhengtangquan@oppo.com>,
<oliver.sang@intel.com>
Subject: Re: [PATCH 2/3] mm: Support tlbbatch flush for a range of PTEs
Date: Mon, 13 Jan 2025 15:30:54 +0800 [thread overview]
Message-ID: <Z4TBLhxvV6llCcWb@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20250113005626.2290-1-21cnbao@gmail.com>
hi, Barry,
On Mon, Jan 13, 2025 at 01:56:26PM +1300, Barry Song wrote:
> On Mon, Jan 6, 2025 at 11:08 PM kernel test robot <lkp@intel.com> wrote:
> >
> > Hi Barry,
> >
> > kernel test robot noticed the following build errors:
> >
> > [auto build test ERROR on akpm-mm/mm-everything]
> >
> > url: https://github.com/intel-lab-lkp/linux/commits/Barry-Song/mm-set-folio-swapbacked-iff-folios-are-dirty-in-try_to_unmap_one/20250106-112638
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
> > patch link: https://lore.kernel.org/r/20250106031711.82855-3-21cnbao%40gmail.com
> > patch subject: [PATCH 2/3] mm: Support tlbbatch flush for a range of PTEs
> > config: riscv-randconfig-001-20250106 (https://download.01.org/0day-ci/archive/20250106/202501061736.FoHcInHJ-lkp@intel.com/config)
> > compiler: riscv64-linux-gcc (GCC) 14.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250106/202501061736.FoHcInHJ-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/202501061736.FoHcInHJ-lkp@intel.com/
> >
>
> Sorry. My bad, does the below diff fix the build?
yes, below diff fixes the build. thanks
Tested-by: kernel test robot <oliver.sang@intel.com>
>
> diff --git a/arch/riscv/include/asm/tlbflush.h b/arch/riscv/include/asm/tlbflush.h
> index 72e559934952..7f3ea687ce33 100644
> --- a/arch/riscv/include/asm/tlbflush.h
> +++ b/arch/riscv/include/asm/tlbflush.h
> @@ -61,7 +61,8 @@ void flush_pmd_tlb_range(struct vm_area_struct *vma, unsigned long start,
> bool arch_tlbbatch_should_defer(struct mm_struct *mm);
> void arch_tlbbatch_add_pending(struct arch_tlbflush_unmap_batch *batch,
> struct mm_struct *mm,
> - unsigned long uaddr);
> + unsigned long uaddr,
> + unsigned long size);
> void arch_flush_tlb_batched_pending(struct mm_struct *mm);
> void arch_tlbbatch_flush(struct arch_tlbflush_unmap_batch *batch);
>
> diff --git a/arch/riscv/mm/tlbflush.c b/arch/riscv/mm/tlbflush.c
> index 9b6e86ce3867..aeda64a36d50 100644
> --- a/arch/riscv/mm/tlbflush.c
> +++ b/arch/riscv/mm/tlbflush.c
> @@ -187,7 +187,8 @@ bool arch_tlbbatch_should_defer(struct mm_struct *mm)
>
> void arch_tlbbatch_add_pending(struct arch_tlbflush_unmap_batch *batch,
> struct mm_struct *mm,
> - unsigned long uaddr)
> + unsigned long uaddr,
> + unsigned long size)
> {
> cpumask_or(&batch->cpumask, &batch->cpumask, mm_cpumask(mm));
> }
>
> > All errors (new ones prefixed by >>):
> >
> > mm/rmap.c: In function 'set_tlb_ubc_flush_pending':
> > >> mm/rmap.c:685:9: error: too many arguments to function 'arch_tlbbatch_add_pending'
> > 685 | arch_tlbbatch_add_pending(&tlb_ubc->arch, mm, uaddr, size);
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~
> > In file included from arch/riscv/include/asm/pgtable.h:113,
> > from include/linux/pgtable.h:6,
> > from include/linux/mm.h:30,
> > from mm/rmap.c:55:
> > arch/riscv/include/asm/tlbflush.h:62:6: note: declared here
> > 62 | void arch_tlbbatch_add_pending(struct arch_tlbflush_unmap_batch *batch,
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~
> >
> >
> > vim +/arch_tlbbatch_add_pending +685 mm/rmap.c
> >
> > 663
> > 664 /*
> > 665 * Bits 0-14 of mm->tlb_flush_batched record pending generations.
> > 666 * Bits 16-30 of mm->tlb_flush_batched bit record flushed generations.
> > 667 */
> > 668 #define TLB_FLUSH_BATCH_FLUSHED_SHIFT 16
> > 669 #define TLB_FLUSH_BATCH_PENDING_MASK \
> > 670 ((1 << (TLB_FLUSH_BATCH_FLUSHED_SHIFT - 1)) - 1)
> > 671 #define TLB_FLUSH_BATCH_PENDING_LARGE \
> > 672 (TLB_FLUSH_BATCH_PENDING_MASK / 2)
> > 673
> > 674 static void set_tlb_ubc_flush_pending(struct mm_struct *mm, pte_t pteval,
> > 675 unsigned long uaddr,
> > 676 unsigned long size)
> > 677 {
> > 678 struct tlbflush_unmap_batch *tlb_ubc = ¤t->tlb_ubc;
> > 679 int batch;
> > 680 bool writable = pte_dirty(pteval);
> > 681
> > 682 if (!pte_accessible(mm, pteval))
> > 683 return;
> > 684
> > > 685 arch_tlbbatch_add_pending(&tlb_ubc->arch, mm, uaddr, size);
> > 686 tlb_ubc->flush_required = true;
> > 687
> > 688 /*
> > 689 * Ensure compiler does not re-order the setting of tlb_flush_batched
> > 690 * before the PTE is cleared.
> > 691 */
> > 692 barrier();
> > 693 batch = atomic_read(&mm->tlb_flush_batched);
> > 694 retry:
> > 695 if ((batch & TLB_FLUSH_BATCH_PENDING_MASK) > TLB_FLUSH_BATCH_PENDING_LARGE) {
> > 696 /*
> > 697 * Prevent `pending' from catching up with `flushed' because of
> > 698 * overflow. Reset `pending' and `flushed' to be 1 and 0 if
> > 699 * `pending' becomes large.
> > 700 */
> > 701 if (!atomic_try_cmpxchg(&mm->tlb_flush_batched, &batch, 1))
> > 702 goto retry;
> > 703 } else {
> > 704 atomic_inc(&mm->tlb_flush_batched);
> > 705 }
> > 706
> > 707 /*
> > 708 * If the PTE was dirty then it's best to assume it's writable. The
> > 709 * caller must use try_to_unmap_flush_dirty() or try_to_unmap_flush()
> > 710 * before the page is queued for IO.
> > 711 */
> > 712 if (writable)
> > 713 tlb_ubc->writable = true;
> > 714 }
> > 715
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
>
next prev parent reply other threads:[~2025-01-13 7:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 3:17 [PATCH 0/3] mm: batched unmap lazyfree large folios during reclamation Barry Song
2025-01-06 3:17 ` [PATCH 1/3] mm: set folio swapbacked iff folios are dirty in try_to_unmap_one Barry Song
2025-01-06 6:40 ` Baolin Wang
2025-01-06 9:03 ` Barry Song
2025-01-06 9:34 ` Baolin Wang
2025-01-06 14:39 ` Lance Yang
2025-01-06 20:52 ` Barry Song
2025-01-06 20:56 ` Barry Song
2025-01-07 1:33 ` Lance Yang
2025-01-06 3:17 ` [PATCH 2/3] mm: Support tlbbatch flush for a range of PTEs Barry Song
2025-01-06 8:22 ` kernel test robot
2025-01-13 0:55 ` Barry Song
2025-01-13 13:13 ` Oliver Sang
2025-01-06 10:07 ` kernel test robot
2025-01-13 0:56 ` Barry Song
2025-01-13 7:30 ` Oliver Sang [this message]
2025-01-06 3:17 ` [PATCH 3/3] mm: Support batched unmap for lazyfree large folios during reclamation Barry Song
2025-01-06 17:28 ` [PATCH 0/3] mm: batched unmap " Lorenzo Stoakes
2025-01-06 19:15 ` Barry Song
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=Z4TBLhxvV6llCcWb@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chrisl@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=gshan@redhat.com \
--cc=hpa@zytor.com \
--cc=ioworker0@gmail.com \
--cc=kasong@tencent.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ryan.roberts@arm.com \
--cc=shahuang@redhat.com \
--cc=tglx@linutronix.de \
--cc=v-songbaohua@oppo.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
--cc=yosryahmed@google.com \
--cc=zhengtangquan@oppo.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