From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-mm@kvack.org
Cc: akpm@linux-foundation.org, naoya.horiguchi@linux.dev,
rostedt@goodmis.org,
Anshuman Khandual <anshuman.khandual@arm.com>
Subject: [PATCH V2 0/2] mm/migration: Add trace events
Date: Tue, 25 Jan 2022 08:38:23 +0530 [thread overview]
Message-ID: <1643080105-11416-1-git-send-email-anshuman.khandual@arm.com> (raw)
This adds trace events for all migration scenarios including base page, THP
and HugeTLB. This series is applies on v5.17-rc1.
Changes in V2:
- Used DECLARE_EVENT_CLASS()/DEFINE_EVENT() construct reducing code footprint
- Added trace events for base page and HugeTLB
Changes in V1:
https://lore.kernel.org/all/1641531575-28524-1-git-send-email-anshuman.khandual@arm.com/
- Dropped mm, pmdp, page arguments from trace
- Updated trace argument names and output format
Changes in RFC:
https://lore.kernel.org/all/1640328398-20698-1-git-send-email-anshuman.khandual@arm.com/
Anshuman Khandual (2):
mm/migration: Add trace events for THP migrations
mm/migration: Add trace events for base page and HugeTLB migrations
include/trace/events/migrate.h | 31 +++++++++++++++++++++++++++++++
include/trace/events/thp.h | 27 +++++++++++++++++++++++++++
mm/huge_memory.c | 5 +++++
mm/migrate.c | 3 +++
mm/rmap.c | 5 +++++
5 files changed, 71 insertions(+)
--
2.20.1
next reply other threads:[~2022-01-25 3:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 3:08 Anshuman Khandual [this message]
2022-01-25 3:08 ` [PATCH V2 1/2] mm/migration: Add trace events for THP migrations Anshuman Khandual
2022-01-25 3:08 ` [PATCH V2 2/2] mm/migration: Add trace events for base page and HugeTLB migrations Anshuman Khandual
2022-01-25 9:41 ` kernel test robot
2022-01-25 9:41 ` kernel test robot
2022-01-25 10:28 ` Anshuman Khandual
2022-01-27 4:07 ` Andrew Morton
2022-01-27 4:52 ` Anshuman Khandual
2022-01-27 6:55 ` Anshuman Khandual
2022-01-25 11:13 ` kernel test robot
2022-01-25 13:28 ` Matthew Wilcox
2022-01-25 15:16 ` Steven Rostedt
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=1643080105-11416-1-git-send-email-anshuman.khandual@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@linux.dev \
--cc=rostedt@goodmis.org \
/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).