From: Yang Shi <yang.shi@linaro.org>
To: akpm@linux-foundation.org, rostedt@goodmis.org, mingo@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linaro-kernel@lists.linaro.org, yang.shi@linaro.org
Subject: [RFC V2] Add gup trace points support
Date: Wed, 2 Dec 2015 14:53:26 -0800 [thread overview]
Message-ID: <1449096813-22436-1-git-send-email-yang.shi@linaro.org> (raw)
Changelog V1 --> V2:
Adopted commetns from Steven
* remove all reference to tsk->comm since it is unnecessary for non-sched
trace points
* reduce arguments for __get_user_pages trace point and update mm/gup.c
accordingly
* Added Ralf's acked-by for patch 4/7.
There is not content change for the trace points in arch specific mm/gup.c.
Some background about why I think this might be useful.
When I was profiling some hugetlb related program, I got page-faults event
doubled when hugetlb is enabled. When I looked into the code, I found page-faults
come from two places, do_page_fault and gup. So, I tried to figure out which
play a role (or both) in my use case. But I can't find existing finer tracing
event for sub page-faults in current mainline kernel.
So, I added the gup trace points support to have finer tracing events for
page-faults. The below events are added:
__get_user_pages
__get_user_pages_fast
fixup_user_fault
Both __get_user_pages and fixup_user_fault call handle_mm_fault.
Just added trace points to raw version __get_user_pages since all variants
will call it finally to do real work.
Although __get_user_pages_fast doesn't call handle_mm_fault, it might be useful
to have it to distinguish between slow and fast version.
Yang Shi (7):
trace/events: Add gup trace events
mm/gup: add gup trace points
x86: mm/gup: add gup trace points
mips: mm/gup: add gup trace points
s390: mm/gup: add gup trace points
sh: mm/gup: add gup trace points
sparc64: mm/gup: add gup trace points
arch/mips/mm/gup.c | 7 +++++++
arch/s390/mm/gup.c | 7 +++++++
arch/sh/mm/gup.c | 8 ++++++++
arch/sparc/mm/gup.c | 8 ++++++++
arch/x86/mm/gup.c | 7 +++++++
include/trace/events/gup.h | 71 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
mm/gup.c | 8 ++++++++
7 files changed, 116 insertions(+)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2015-12-02 23:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 22:53 Yang Shi [this message]
2015-12-02 22:53 ` [PATCH V2 1/7] trace/events: Add gup trace events Yang Shi
2015-12-03 4:07 ` Steven Rostedt
2015-12-03 18:36 ` Shi, Yang
2015-12-02 22:53 ` [PATCH V2 2/7] mm/gup: add gup trace points Yang Shi
2015-12-02 23:36 ` Dave Hansen
2015-12-03 0:11 ` Shi, Yang
2015-12-03 0:52 ` Shi, Yang
2015-12-03 4:13 ` Steven Rostedt
2015-12-03 18:36 ` Shi, Yang
2015-12-03 19:06 ` Steven Rostedt
2015-12-03 22:10 ` Shi, Yang
2015-12-02 22:53 ` [PATCH V2 3/7] x86: " Yang Shi
2015-12-02 22:53 ` [PATCH V2 4/7] mips: " Yang Shi
2015-12-02 22:53 ` [PATCH V2 5/7] s390: " Yang Shi
2015-12-02 22:53 ` [PATCH V2 6/7] sh: " Yang Shi
2015-12-02 22:53 ` [PATCH V2 7/7] sparc64: " Yang Shi
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=1449096813-22436-1-git-send-email-yang.shi@linaro.org \
--to=yang.shi@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--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).