linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Naoya Horiguchi <naoya.horiguchi@linux.dev>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-mm@kvack.org, Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Zi Yan <ziy@nvidia.com>,
	Naoya Horiguchi <naoya.horiguchi@nec.com>,
	John Hubbard <jhubbard@nvidia.com>,
	Matthew Wilcox <willy@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/migration: Add trace events for THP migrations
Date: Tue, 11 Jan 2022 15:57:56 +0900	[thread overview]
Message-ID: <20220111065756.GA808887@u2004> (raw)
In-Reply-To: <ee99799c-4e88-a7f5-0ec2-64cd710051e5@arm.com>

On Tue, Jan 11, 2022 at 10:31:21AM +0530, Anshuman Khandual wrote:
> 
> 
> On 1/11/22 7:28 AM, Naoya Horiguchi wrote:
> > Hi Anshuman,
> > 
> > On Fri, Jan 07, 2022 at 10:29:35AM +0530, Anshuman Khandual wrote:
> >> This adds two trace events for PMD based THP migration without split. These
> >> events closely follow the implementation details like setting and removing
> >> of PMD migration entries, which are essential operations for THP migration.
> > 
> > I often want to check which individual pages are migrated to which places
> > (or not migrated) for testing, so these new tracepoints could help me.
> > Maybe these can be much greater if they can handle other types of page
> > migration for raw pages and hugetlb pages.  Is it hard to cover all such
> > page migration events?
> 
> Are you suggesting to cover all migration entry transitions for normal
> and HugeTLB pages as well ?

Yes if you like the idea. I think that some events listed below can be grouped
into one tracepoint event with showing args like pgsize or read/write flags
(or implementation detail is up to you).

> 
> migrate_pages()
> 	unmap_and_move_huge_page()
> 		try_to_migrate()
> 			make_writable_migration_entry() <---
> 			make_readable_migration_entry() <---
> 		remove_migration_ptes() <---
> 	unmap_and_move()
> 		__unmap_and_move()
> 			try_to_migrate()
> 				make_writable_migration_entry() <---
> 				make_readable_migration_entry() <---
> 			remove_migration_ptes() <---

Thanks,
Naoya Horiguchi


  reply	other threads:[~2022-01-11  6:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07  4:59 [PATCH] mm/migration: Add trace events for THP migrations Anshuman Khandual
2022-01-10 17:03 ` Steven Rostedt
2022-01-11  4:07   ` Anshuman Khandual
2022-01-11  1:58 ` Naoya Horiguchi
2022-01-11  5:01   ` Anshuman Khandual
2022-01-11  6:57     ` Naoya Horiguchi [this message]
2022-01-21  6:38       ` Anshuman Khandual
2022-01-24 14:06         ` Naoya Horiguchi

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=20220111065756.GA808887@u2004 \
    --to=naoya.horiguchi@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=naoya.horiguchi@nec.com \
    --cc=rostedt@goodmis.org \
    --cc=willy@infradead.org \
    --cc=ziy@nvidia.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).