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,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH v4 3/7] x86: mm/gup: add gup trace points
Date: Wed, 9 Dec 2015 13:27:59 -0800 [thread overview]
Message-ID: <56689CDF.8060708@linaro.org> (raw)
In-Reply-To: <20151209160749.250a2f56@gandalf.local.home>
On 12/9/2015 1:07 PM, Steven Rostedt wrote:
> On Wed, 9 Dec 2015 09:29:20 -0800
> Yang Shi <yang.shi@linaro.org> wrote:
>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Ingo Molnar <mingo@redhat.com>
>> Cc: "H. Peter Anvin" <hpa@zytor.com>
>> Cc: x86@kernel.org
>> Signed-off-by: Yang Shi <yang.shi@linaro.org>
>> ---
>> arch/x86/mm/gup.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/arch/x86/mm/gup.c b/arch/x86/mm/gup.c
>> index ae9a37b..a96bcb7 100644
>> --- a/arch/x86/mm/gup.c
>> +++ b/arch/x86/mm/gup.c
>> @@ -12,6 +12,9 @@
>>
>> #include <asm/pgtable.h>
>>
>> +#define CREATE_TRACE_POINTS
>> +#include <trace/events/gup.h>>
>
> First off, does the above even compile?
>
> Second, you already created the tracepoints in mm/gup.c, why are you
> creating them here again? CREATE_TRACE_POINTS must be defined only once
> per events/.h file.
Sorry for that. The typo was introduced by git amend without running
test build. The multiple definition of trace points was not caught by my
shaky test script.
Will fix them soon.
Thanks,
Yang
>
> -- Steve
>
>> +
>> static inline pte_t gup_get_pte(pte_t *ptep)
>> {
>> #ifndef CONFIG_X86_PAE
>> @@ -270,6 +273,8 @@ int __get_user_pages_fast(unsigned long start, int nr_pages, int write,
>> (void __user *)start, len)))
>> return 0;
>>
>> + trace_gup_get_user_pages_fast(start, nr_pages);
>> +
>> /*
>> * XXX: batch / limit 'nr', to avoid large irq off latency
>> * needs some instrumenting to determine the common sizes used by
>> @@ -373,6 +378,8 @@ int get_user_pages_fast(unsigned long start, int nr_pages, int write,
>> } while (pgdp++, addr = next, addr != end);
>> local_irq_enable();
>>
>> + trace_gup_get_user_pages_fast(start, nr_pages);
>> +
>> VM_BUG_ON(nr != (end - start) >> PAGE_SHIFT);
>> return nr;
>>
>
--
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-09 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 17:29 [RFC V4] Add gup trace points support Yang Shi
2015-12-09 17:29 ` [PATCH v4 1/7] trace/events: Add gup trace events Yang Shi
2015-12-09 17:29 ` [PATCH v4 2/7] mm/gup: add gup trace points Yang Shi
2015-12-09 17:29 ` [PATCH v4 3/7] x86: " Yang Shi
2015-12-09 21:07 ` Steven Rostedt
2015-12-09 21:27 ` Shi, Yang [this message]
2015-12-09 17:29 ` [PATCH v4 4/7] mips: " Yang Shi
2015-12-09 17:29 ` [PATCH v4 5/7] s390: " Yang Shi
2015-12-09 17:29 ` [PATCH v4 6/7] sh: " Yang Shi
2015-12-09 17:29 ` [PATCH v4 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=56689CDF.8060708@linaro.org \
--to=yang.shi@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--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 \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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).