From: Steven Rostedt <rostedt@goodmis.org>
To: Yang Shi <yang.shi@linaro.org>
Cc: akpm@linux-foundation.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH v3 2/7] mm/gup: add gup trace points
Date: Tue, 8 Dec 2015 15:25:55 -0500 [thread overview]
Message-ID: <20151208152555.1c03ae54@gandalf.local.home> (raw)
In-Reply-To: <1449603595-718-3-git-send-email-yang.shi@linaro.org>
On Tue, 8 Dec 2015 11:39:50 -0800
Yang Shi <yang.shi@linaro.org> wrote:
> For slow version, just add trace point for raw __get_user_pages since all
> slow variants call it to do the real work finally.
>
> Signed-off-by: Yang Shi <yang.shi@linaro.org>
> ---
> mm/gup.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/mm/gup.c b/mm/gup.c
> index deafa2c..44f05c9 100644
> --- a/mm/gup.c
> +++ b/mm/gup.c
> @@ -18,6 +18,9 @@
>
> #include "internal.h"
>
> +#define CREATE_TRACE_POINTS
> +#include <trace/events/gup.h>
> +
> static struct page *no_page_table(struct vm_area_struct *vma,
> unsigned int flags)
> {
> @@ -462,6 +465,8 @@ long __get_user_pages(struct task_struct *tsk, struct mm_struct *mm,
> if (!nr_pages)
> return 0;
>
> + trace_gup_get_user_pages(start, nr_pages);
> +
> VM_BUG_ON(!!pages != !!(gup_flags & FOLL_GET));
>
> /*
> @@ -599,6 +604,7 @@ int fixup_user_fault(struct task_struct *tsk, struct mm_struct *mm,
> if (!(vm_flags & vma->vm_flags))
> return -EFAULT;
>
> + trace_gup_fixup_user_fault(address);
> ret = handle_mm_fault(mm, vma, address, fault_flags);
> if (ret & VM_FAULT_ERROR) {
> if (ret & VM_FAULT_OOM)
> @@ -1340,6 +1346,8 @@ int __get_user_pages_fast(unsigned long start, int nr_pages, int write,
> start, len)))
> return 0;
>
> + trace_gup_get_user_pages_fast(start, (unsigned long) nr_pages);
typecast shouldn't be needed. But I'm wondering, it would save space in
the ring buffer if we used unsigend int instead of long. Will nr_pages
ever be bigger than 4 billion?
-- Steve
> +
> /*
> * Disable interrupts. We use the nested form as we can already have
> * interrupts disabled by get_futex_key.
--
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 prev parent reply other threads:[~2015-12-08 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 19:39 [RFC V3] Add gup trace points support Yang Shi
2015-12-08 19:39 ` [PATCH v3 1/7] trace/events: Add gup trace events Yang Shi
2015-12-08 19:39 ` [PATCH v3 2/7] mm/gup: add gup trace points Yang Shi
2015-12-08 20:25 ` Steven Rostedt [this message]
2015-12-08 20:58 ` Shi, Yang
2015-12-08 19:39 ` [PATCH v3 3/7] x86: " Yang Shi
2015-12-08 19:39 ` [PATCH v3 4/7] mips: " Yang Shi
2015-12-08 19:39 ` [PATCH v3 5/7] s390: " Yang Shi
2015-12-08 19:39 ` [PATCH v3 6/7] sh: " Yang Shi
2015-12-08 19:39 ` [PATCH v3 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=20151208152555.1c03ae54@gandalf.local.home \
--to=rostedt@goodmis.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=yang.shi@linaro.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).