From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755498AbbCCJOS (ORCPT ); Tue, 3 Mar 2015 04:14:18 -0500 Received: from e23smtp02.au.ibm.com ([202.81.31.144]:43613 "EHLO e23smtp02.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751445AbbCCJOO (ORCPT ); Tue, 3 Mar 2015 04:14:14 -0500 From: "Aneesh Kumar K.V" To: Stefan Strogin , linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: Stefan Strogin , Joonsoo Kim , Andrew Morton , Marek Szyprowski , Michal Nazarewicz , Laurent Pinchart , Dmitry Safonov , Pintu Kumar , Weijie Yang , Laura Abbott , SeongJae Park , Hui Zhu , Minchan Kim , Dyasly Sergey , Vyacheslav Tyrtov , Aleksei Mateosian , gregory.0xf0@gmail.com, sasha.levin@oracle.com, gioh.kim@lge.com, pavel@ucw.cz, stefan.strogin@gmail.com Subject: Re: [PATCH v3 1/4] mm: cma: add trace events to debug physically-contiguous memory allocations In-Reply-To: <9ae4c45b49e8df6e079448550c2b81ade5d3603a.1424802755.git.s.strogin@partner.samsung.com> References: <9ae4c45b49e8df6e079448550c2b81ade5d3603a.1424802755.git.s.strogin@partner.samsung.com> User-Agent: Notmuch/0.19+30~gd241a48 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Tue, 03 Mar 2015 14:43:00 +0530 Message-ID: <87sidma1gj.fsf@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15030309-0005-0000-0000-0000016529B4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Stefan Strogin writes: > Add trace events for cma_alloc() and cma_release(). > > Signed-off-by: Stefan Strogin > --- > include/trace/events/cma.h | 57 ++++++++++++++++++++++++++++++++++++++++++++++ > mm/cma.c | 6 +++++ > 2 files changed, 63 insertions(+) > create mode 100644 include/trace/events/cma.h > > diff --git a/include/trace/events/cma.h b/include/trace/events/cma.h > new file mode 100644 > index 0000000..3fe7a56 > --- /dev/null > +++ b/include/trace/events/cma.h > @@ -0,0 +1,57 @@ > +#undef TRACE_SYSTEM > +#define TRACE_SYSTEM cma > + > +#if !defined(_TRACE_CMA_H) || defined(TRACE_HEADER_MULTI_READ) > +#define _TRACE_CMA_H > + > +#include > +#include > + > +TRACE_EVENT(cma_alloc, > + > + TP_PROTO(struct cma *cma, unsigned long pfn, int count), > + > + TP_ARGS(cma, pfn, count), > + > + TP_STRUCT__entry( > + __field(unsigned long, pfn) > + __field(unsigned long, count) > + ), > + > + TP_fast_assign( > + __entry->pfn = pfn; > + __entry->count = count; > + ), > + > + TP_printk("pfn=%lu page=%p count=%lu\n", > + __entry->pfn, > + pfn_to_page(__entry->pfn), > + __entry->count) > +); > + > +TRACE_EVENT(cma_release, > + > + TP_PROTO(struct cma *cma, unsigned long pfn, int count), > + > + TP_ARGS(cma, pfn, count), > + > + TP_STRUCT__entry( > + __field(unsigned long, pfn) > + __field(unsigned long, count) > + ), > + > + TP_fast_assign( > + __entry->pfn = pfn; > + __entry->count = count; > + ), > + > + TP_printk("pfn=%lu page=%p count=%lu\n", > + __entry->pfn, > + pfn_to_page(__entry->pfn), > + __entry->count) > +); > + > +#endif /* _TRACE_CMA_H */ > + > +/* This part must be outside protection */ > +#include > diff --git a/mm/cma.c b/mm/cma.c > index 9e3d44a..3a63c96 100644 > --- a/mm/cma.c > +++ b/mm/cma.c > @@ -23,6 +23,7 @@ > # define DEBUG > #endif > #endif > +#define CREATE_TRACE_POINTS > > #include > #include > @@ -34,6 +35,7 @@ > #include > #include > #include > +#include > > #include "cma.h" > > @@ -408,6 +410,9 @@ struct page *cma_alloc(struct cma *cma, int count, unsigned int align) > start = bitmap_no + mask + 1; > } > > + if (page) > + trace_cma_alloc(cma, pfn, count); > + > pr_debug("%s(): returned %p\n", __func__, page); > return page; > } > @@ -440,6 +445,7 @@ bool cma_release(struct cma *cma, struct page *pages, int count) > > free_contig_range(pfn, count); > cma_clear_bitmap(cma, pfn, count); > + trace_cma_release(cma, pfn, count); > > return true; Are we interested only in successful allocation and release ? Should we also have the trace point carry information regarding failure ? -aneesh