From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932580AbbCEOde (ORCPT ); Thu, 5 Mar 2015 09:33:34 -0500 Received: from mailout2.w1.samsung.com ([210.118.77.12]:33471 "EHLO mailout2.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753240AbbCEOda (ORCPT ); Thu, 5 Mar 2015 09:33:30 -0500 X-AuditID: cbfec7f4-b7f126d000001e9a-c0-54f868a608fa Message-id: <54F86933.6040203@partner.samsung.com> Date: Thu, 05 Mar 2015 17:33:23 +0300 From: Stefan Strogin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-version: 1.0 To: "Aneesh Kumar K.V" , linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: 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 References: <9ae4c45b49e8df6e079448550c2b81ade5d3603a.1424802755.git.s.strogin@partner.samsung.com> <87sidma1gj.fsf@linux.vnet.ibm.com> In-reply-to: <87sidma1gj.fsf@linux.vnet.ibm.com> Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrIIsWRmVeSWpSXmKPExsVy+t/xa7rLMn6EGLT8V7F4OG8Su8Wc9WvY LB6/nsdi8WnlUzaLZ01fGC2mTd/AarGyu5nNYnvnDHaLzolL2C0u75rDZnFvzX9Wi7VH7rJb LDjewmqx7Ot7dou7p46yWfR9P8xuMXm2lMW3k3OYLRYfuc1scW1HP5PF5Tf/2S2mzvjBbnFy w1lWiw3NXA4SHpf7epk8ds66y+4xu2Mmq8emVZ1sHps+TWL36Hp7hcnjxIzfLB4PDm1m8Vj3 5xWTx8ent1g8Dr7bw+TRt2UVo8eK1d/ZPT5vkvPo2viLNYA/issmJTUnsyy1SN8ugStj4evf LAUN7BW/2i6xNzDuZ+1i5OSQEDCROHb7DjOELSZx4d56NhBbSGApo8SWDv8uRi4g+yOjxNzp M8ESvAJGEheuLgKzWQRUJSYeXAM2iA1k0IXpjF2MHByiAhESty9zQpQLSvyYfI8FxBYRyJHo ae5hBpnJLPCIVWLiqSlgi4UFMiUufHvADLHsAKPEybZ5jCAJTgEDiQ/HNzKBDGUWUJeYMiUX JMwsIC+xec1b5gmMArOQ7JiFUDULSdUCRuZVjKKppckFxUnpuYZ6xYm5xaV56XrJ+bmbGCHR /mUH4+JjVocYBTgYlXh4C5K+hQixJpYVV+YeYpTgYFYS4b0S+SNEiDclsbIqtSg/vqg0J7X4 ECMTB6dUA6NDccPsle9cfS/en6Nvv2XBGqXXP5c6H78seb3gac/Ji5w/P+gkqyqZVtUs2fgm 4LHC/J3PFM9dm5B18o1igKOd9yy+w+v/bZjHeuFN5x1zhv+nT8t3e0884/TyWqNv1HQp51ud Xoq9L3cXX559c86090dvhxX8TFLNvl3ftXGpXdbP87d8XLY8V2Ipzkg01GIuKk4EAPzGFsrU AgAA Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Aneesh, On 03/03/15 12:13, Aneesh Kumar K.V wrote: > > Are we interested only in successful allocation and release ? Should we also > have the trace point carry information regarding failure ? > > -aneesh > I think we actually can be interested in tracing allocation failures too. Thanks for the remark. Should it be smth like that? @@ -408,6 +410,8 @@ struct page *cma_alloc(struct cma *cma, int count, unsigned int align) start = bitmap_no + mask + 1; } + trace_cma_alloc(cma, page, count); + pr_debug("%s(): returned %p\n", __func__, page); return page; } and in include/trace/events/cma.h: +TRACE_EVENT(cma_alloc, <...> + TP_fast_assign( + __entry->page = page; + __entry->count = count; + ), + + TP_printk("page=%p pfn=%lu count=%lu\n", + __entry->page, + __entry->page ? page_to_pfn(__entry->page) : 0, + __entry->count)