linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mircea CIRJALIU - MELIU <mcirjaliu@bitdefender.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jerome Glisse <jglisse@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"aarcange@redhat.com" <aarcange@redhat.com>
Subject: [RFC PATCH v1 2/4] mm: also set VMA in khugepaged range invalidation
Date: Wed, 11 Dec 2019 09:29:21 +0000	[thread overview]
Message-ID: <DB7PR02MB3979E79A7ADF7E7B2F397418BB5A0@DB7PR02MB3979.eurprd02.prod.outlook.com> (raw)

MMU notifier client may need the VMA for extra info.
This change is needed by the remote mapping feature that inspects anon VMAs
with huge mappings. 

Signed-off-by: Mircea Cirjaliu <mcirjaliu@bitdefender.com>
---
 mm/khugepaged.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mm/khugepaged.c b/mm/khugepaged.c
index b679908..11c65f3 100644
--- a/mm/khugepaged.c
+++ b/mm/khugepaged.c
@@ -1028,7 +1028,7 @@ static void collapse_huge_page(struct mm_struct *mm,
 
 	anon_vma_lock_write(vma->anon_vma);
 
-	mmu_notifier_range_init(&range, MMU_NOTIFY_CLEAR, 0, NULL, mm,
+	mmu_notifier_range_init(&range, MMU_NOTIFY_CLEAR, 0, vma, mm,
 				address, address + HPAGE_PMD_SIZE);
 	mmu_notifier_invalidate_range_start(&range);


             reply	other threads:[~2019-12-11  9:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11  9:29 Mircea CIRJALIU - MELIU [this message]
2019-12-11 15:44 ` [RFC PATCH v1 2/4] mm: also set VMA in khugepaged range invalidation Kirill A. Shutemov
2019-12-11 16:16   ` Mircea CIRJALIU - MELIU

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=DB7PR02MB3979E79A7ADF7E7B2F397418BB5A0@DB7PR02MB3979.eurprd02.prod.outlook.com \
    --to=mcirjaliu@bitdefender.com \
    --cc=aarcange@redhat.com \
    --cc=jglisse@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pbonzini@redhat.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;
as well as URLs for NNTP newsgroup(s).