From: Yin Fengwei <fengwei.yin@intel.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
yuzhao@google.com, ryan.roberts@arm.com, shy828301@gmail.com,
akpm@linux-foundation.org, willy@infradead.org, david@redhat.com
Cc: fengwei.yin@intel.com
Subject: [RFC PATCH 1/3] mm: add function folio_in_range()
Date: Sat, 8 Jul 2023 00:52:19 +0800 [thread overview]
Message-ID: <20230707165221.4076590-2-fengwei.yin@intel.com> (raw)
In-Reply-To: <20230707165221.4076590-1-fengwei.yin@intel.com>
It will be used to check whether the folio is mapped to specific
VMA and whether the mapping address of folio is in the range.
Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
---
mm/internal.h | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/mm/internal.h b/mm/internal.h
index f1276d90484ad..66117523d7d71 100644
--- a/mm/internal.h
+++ b/mm/internal.h
@@ -585,6 +585,32 @@ extern long faultin_vma_page_range(struct vm_area_struct *vma,
bool write, int *locked);
extern bool mlock_future_ok(struct mm_struct *mm, unsigned long flags,
unsigned long bytes);
+
+static inline bool
+folio_in_range(struct folio *folio, struct vm_area_struct *vma,
+ unsigned long start, unsigned long end)
+{
+ pgoff_t pgoff, addr;
+ unsigned long vma_pglen = (vma->vm_end - vma->vm_start) >> PAGE_SHIFT;
+
+ VM_WARN_ON_FOLIO(folio_test_ksm(folio), folio);
+ if (start < vma->vm_start)
+ start = vma->vm_start;
+
+ if (end > vma->vm_end)
+ end = vma->vm_end;
+
+ pgoff = folio_pgoff(folio);
+
+ /* if folio start address is not in vma range */
+ if (pgoff < vma->vm_pgoff || pgoff > vma->vm_pgoff + vma_pglen)
+ return false;
+
+ addr = vma->vm_start + ((pgoff - vma->vm_pgoff) << PAGE_SHIFT);
+
+ return ((addr >= start) && (addr + folio_size(folio) <= end));
+}
+
/*
* mlock_vma_folio() and munlock_vma_folio():
* should be called with vma's mmap_lock held for read or write,
--
2.39.2
next prev parent reply other threads:[~2023-07-07 16:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 16:52 [RFC PATCH 0/3] support large folio for mlock Yin Fengwei
2023-07-07 16:52 ` Yin Fengwei [this message]
2023-07-08 5:47 ` [RFC PATCH 1/3] mm: add function folio_in_range() Yu Zhao
2023-07-08 6:44 ` Yin, Fengwei
2023-07-07 16:52 ` [RFC PATCH 2/3] mm: handle large folio when large folio in VM_LOCKED VMA range Yin Fengwei
2023-07-08 5:11 ` Yu Zhao
2023-07-08 5:33 ` Yin, Fengwei
2023-07-08 5:56 ` Yu Zhao
2023-07-07 16:52 ` [RFC PATCH 3/3] mm: mlock: update mlock_pte_range to handle large folio Yin Fengwei
2023-07-07 17:26 ` [RFC PATCH 0/3] support large folio for mlock Matthew Wilcox
2023-07-07 18:54 ` David Hildenbrand
2023-07-07 19:06 ` Matthew Wilcox
2023-07-07 19:15 ` David Hildenbrand
2023-07-07 19:26 ` Matthew Wilcox
2023-07-10 10:36 ` Ryan Roberts
2023-07-08 3:52 ` Yin, Fengwei
2023-07-08 4:02 ` Matthew Wilcox
2023-07-08 4:35 ` Yu Zhao
2023-07-08 4:40 ` Yin, Fengwei
2023-07-08 4:36 ` Yin, Fengwei
2023-07-09 13:25 ` Yin, Fengwei
2023-07-10 9:32 ` David Hildenbrand
2023-07-10 9:43 ` Yin, Fengwei
2023-07-10 9:57 ` David Hildenbrand
2023-07-10 10:19 ` Yin, Fengwei
2023-07-08 3:34 ` Yin, Fengwei
2023-07-08 3:31 ` Yin, Fengwei
2023-07-08 4:45 ` Yu Zhao
2023-07-08 5:01 ` Yin, Fengwei
2023-07-08 5:06 ` Yu Zhao
2023-07-08 5:35 ` Yin, Fengwei
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=20230707165221.4076590-2-fengwei.yin@intel.com \
--to=fengwei.yin@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=willy@infradead.org \
--cc=yuzhao@google.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