linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Shi, Yang" <yang.shi@linaro.org>
To: Steven Rostedt <rostedt@goodmis.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 1/7] trace/events: Add gup trace events
Date: Tue, 01 Dec 2015 16:39:24 -0800	[thread overview]
Message-ID: <565E3DBC.9070204@linaro.org> (raw)
In-Reply-To: <20151201191826.771bce5d@gandalf.local.home>

On 12/1/2015 4:18 PM, Steven Rostedt wrote:
> On Tue, 01 Dec 2015 16:07:44 -0800
> "Shi, Yang" <yang.shi@linaro.org> wrote:
>
>> On 12/1/2015 3:56 PM, Steven Rostedt wrote:
>>> On Tue,  1 Dec 2015 15:06:11 -0800
>>> Yang Shi <yang.shi@linaro.org> wrote:
>>>
>>>> page-faults events record the invoke to handle_mm_fault, but the invoke
>>>> may come from do_page_fault or gup. In some use cases, the finer event count
>>>> mey be needed, so add trace events support for:
>>>>
>>>> __get_user_pages
>>>> __get_user_pages_fast
>>>> fixup_user_fault
>>>>
>>>> Signed-off-by: Yang Shi <yang.shi@linaro.org>
>>>> ---
>>>>    include/trace/events/gup.h | 77 ++++++++++++++++++++++++++++++++++++++++++++++
>>>>    1 file changed, 77 insertions(+)
>>>>    create mode 100644 include/trace/events/gup.h
>>>>
>>>> diff --git a/include/trace/events/gup.h b/include/trace/events/gup.h
>>>> new file mode 100644
>>>> index 0000000..37d18f9
>>>> --- /dev/null
>>>> +++ b/include/trace/events/gup.h
>>>> @@ -0,0 +1,77 @@
>>>> +#undef TRACE_SYSTEM
>>>> +#define TRACE_SYSTEM gup
>>>> +
>>>> +#if !defined(_TRACE_GUP_H) || defined(TRACE_HEADER_MULTI_READ)
>>>> +#define _TRACE_GUP_H
>>>> +
>>>> +#include <linux/types.h>
>>>> +#include <linux/tracepoint.h>
>>>> +
>>>> +TRACE_EVENT(gup_fixup_user_fault,
>>>> +
>>>> +	TP_PROTO(struct task_struct *tsk, struct mm_struct *mm,
>>>> +			unsigned long address, unsigned int fault_flags),
>>>> +
>>>> +	TP_ARGS(tsk, mm, address, fault_flags),
>>>> +
>>>> +	TP_STRUCT__entry(
>>>> +		__array(	char,	comm,	TASK_COMM_LEN	)
>>>
>>> Why save the comm? The tracing infrastructure should keep track of that.
>>
>> The code is referred to kmem.h which has comm copied. If it is
>> unnecessary, it definitely could be removed.
>
> Sometimes comm isn't that reliable. But really, the only tracepoint
> that should record it is sched_switch, and sched_wakeup. With those
> two, the rest of the trace points should be fine.
>
>>
>>>
>>>> +		__field(	unsigned long,	address		)
>>>> +	),
>>>> +
>>>> +	TP_fast_assign(
>>>> +		memcpy(__entry->comm, tsk->comm, TASK_COMM_LEN);
>>>> +		__entry->address	= address;
>>>> +	),
>>>> +
>>>> +	TP_printk("comm=%s address=%lx", __entry->comm, __entry->address)
>>>> +);
>>>> +
>>>> +TRACE_EVENT(gup_get_user_pages,
>>>> +
>>>> +	TP_PROTO(struct task_struct *tsk, struct mm_struct *mm,
>>>> +			unsigned long start, unsigned long nr_pages,
>>>> +			unsigned int gup_flags, struct page **pages,
>>>> +			struct vm_area_struct **vmas, int *nonblocking),
>>>> +
>>>> +	TP_ARGS(tsk, mm, start, nr_pages, gup_flags, pages, vmas, nonblocking),
>>>
>>> Why so many arguments? Most are not used.
>>
>> My understanding to TP_ARGS may be not right. Doesn't it require all the
>> args defined by the function? If not, it could definitely be shrunk.
>> Just need keep the args used by TP_printk?
>
> It only needs what is used by TP_fast_assign().

Thanks, will fix them in V2.

Yang

>
> -- Steve
>

--
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>

  reply	other threads:[~2015-12-02  0:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 23:06 [RFC] Add gup trace points support Yang Shi
2015-12-01 23:06 ` [PATCH 1/7] trace/events: Add gup trace events Yang Shi
2015-12-01 23:56   ` Steven Rostedt
2015-12-02  0:07     ` Shi, Yang
2015-12-02  0:18       ` Steven Rostedt
2015-12-02  0:39         ` Shi, Yang [this message]
2015-12-01 23:06 ` [PATCH 2/7] mm/gup: add gup trace points Yang Shi
2015-12-01 23:06 ` [PATCH 3/7] x86: " Yang Shi
2015-12-01 23:06 ` [PATCH 4/7] mips: " Yang Shi
2015-12-02 13:23   ` Ralf Baechle
2015-12-01 23:06 ` [PATCH 5/7] s390: " Yang Shi
2015-12-01 23:06 ` [PATCH 6/7] sh: " Yang Shi
2015-12-01 23:06 ` [PATCH 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=565E3DBC.9070204@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).