From: Ebru Akagunduz <ebru.akagunduz@gmail.com>
To: Rik van Riel <riel@redhat.com>, Vlastimil Babka <vbabka@suse.cz>
Cc: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
n-horiguchi@ah.jp.nec.com, aarcange@redhat.com,
iamjoonsoo.kim@lge.com, xiexiuqi@huawei.com, gorcunov@openvz.org,
linux-kernel@vger.kernel.org, mgorman@suse.de,
rientjes@google.com, aneesh.kumar@linux.vnet.ibm.com,
hughd@google.com, hannes@cmpxchg.org, mhocko@suse.cz,
boaz@plexistor.com, raindel@mellanox.com, linux-mm@kvack.org
Subject: Re: [RESEND RFC v4 1/3] mm: add tracepoint for scanning pages
Date: Sat, 5 Sep 2015 22:24:48 +0300 [thread overview]
Message-ID: <20150905192448.GA3933@debian> (raw)
In-Reply-To: <55E9CA8B.7090004@redhat.com>
On Fri, Sep 04, 2015 at 12:44:59PM -0400, Rik van Riel wrote:
> On 09/04/2015 12:07 PM, Vlastimil Babka wrote:
> > On 09/03/2015 10:51 PM, Ebru Akagunduz wrote:
> >> Using static tracepoints, data of functions is recorded.
> >> It is good to automatize debugging without doing a lot
> >> of changes in the source code.
> >>
> >> This patch adds tracepoint for khugepaged_scan_pmd,
> >> collapse_huge_page and __collapse_huge_page_isolate.
> >>
> >> Signed-off-by: Ebru Akagunduz <ebru.akagunduz@gmail.com>
> >> Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> >> Acked-by: Rik van Riel <riel@redhat.com>
> >> ---
> >> Changes in v2:
> >> - Nothing changed
> >>
> >> Changes in v3:
> >> - Print page address instead of vm_start (Vlastimil Babka)
> >> - Define constants to specify exact tracepoint result (Vlastimil Babka)
> >>
> >> Changes in v4:
> >> - Change the constant prefix with SCAN_ instead of MM_ (Vlastimil Babka)
> >> - Move the constants into the enum (Vlastimil Babka)
> >> - Move the constants from mm.h to huge_memory.c
> >> (because only will be used in huge_memory.c) (Vlastimil Babka)
> >> - Print pfn in tracepoints (Vlastimil Babka)
> >> - Print scan result as string in tracepoint (Vlastimil Babka)
> >> (I tried to make same things to print string like mm/compaction.c.
> >> My patch does not print string, I skip something but could not see why)
> >
> > How do you print the trace? Do you cat /sys/kernel/debug/tracing/trace_pipe
> > or use some tool such as trace-cmd? I have just recently realized that tools
> > don't print strings in the compaction tracepoints, which lead to a patch [1].
> > You could convert this patch in the same way and then it should work with
> > tracing tools. Sorry for previously suggesting a wrong example to follow.
> >
> > [1] https://lkml.org/lkml/2015/8/27/373
I use perf tool to test changes.
>
> Well that explains why doing the same thing as compaction.c
> resulted in the strings not being printed! Ebru and I got
> confused over that for quite a while :)
>
> Thanks for pointing us to the fix.
>
> Ebru, can you use tracepoint macros like in Vlastimil's patch
> above, so your tracepoints work?
>
I did similar changes with Vlastimil's patch. It works!
Thanks,
Ebru
--
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-09-05 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 20:51 [RESEND RFC v4 0/3] mm: make swapin readahead to gain more thp performance Ebru Akagunduz
2015-09-03 20:51 ` [RESEND RFC v4 1/3] mm: add tracepoint for scanning pages Ebru Akagunduz
2015-09-04 16:07 ` Vlastimil Babka
2015-09-04 16:44 ` Rik van Riel
2015-09-05 19:24 ` Ebru Akagunduz [this message]
2015-09-03 20:51 ` [RESEND RFC v4 2/3] mm: make optimistic check for swapin readahead Ebru Akagunduz
2015-09-04 16:18 ` Vlastimil Babka
2015-09-03 20:51 ` [RESEND RFC v4 3/3] mm: make swapin readahead to improve thp collapse rate Ebru Akagunduz
2015-09-04 16:44 ` Vlastimil Babka
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=20150905192448.GA3933@debian \
--to=ebru.akagunduz@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=boaz@plexistor.com \
--cc=gorcunov@openvz.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=raindel@mellanox.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=xiexiuqi@huawei.com \
/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).