From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752386AbbCQHkd (ORCPT ); Tue, 17 Mar 2015 03:40:33 -0400 Received: from mail-wg0-f51.google.com ([74.125.82.51]:33453 "EHLO mail-wg0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751268AbbCQHkb (ORCPT ); Tue, 17 Mar 2015 03:40:31 -0400 Date: Tue, 17 Mar 2015 08:40:25 +0100 From: Ingo Molnar To: Stefan Strogin Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Joonsoo Kim , Andrew Morton , Marek Szyprowski , Michal Nazarewicz , aneesh.kumar@linux.vnet.ibm.com, 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, Steven Rostedt , Ingo Molnar Subject: Re: [PATCH v4 1/5] mm: cma: add trace events to debug physically-contiguous memory allocations Message-ID: <20150317074025.GA27548@gmail.com> References: <550741BD.9080109@partner.samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <550741BD.9080109@partner.samsung.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Stefan Strogin wrote: > > +TRACE_EVENT(cma_alloc, > > + > > + TP_PROTO(struct cma *cma, struct page *page, int count), > > + > > + TP_ARGS(cma, page, count), > > + > > + TP_STRUCT__entry( > > + __field(struct page *, page) > > + __field(unsigned long, count) > > + ), > > + > > + TP_fast_assign( > > + __entry->page = page; > > + __entry->count = count; > > + ), > > + > > + TP_printk("page=%p pfn=%lu count=%lu", > > + __entry->page, > > + __entry->page ? page_to_pfn(__entry->page) : 0, > > + __entry->count) So I'm wondering, the fast-assign side is not equivalent to the TP_printk() side: > > + __entry->page = page; > > + __entry->page ? page_to_pfn(__entry->page) : 0, to me it seems it would be useful if MM tracing standardized on pfn printing. Just like you did for trace_cma_release(). Also: > > + __entry->page ? page_to_pfn(__entry->page) : 0, pfn 0 should probably be reserved for the true 0th pfn - those exist in some machines. Returning -1ll could be the 'no such pfn' condition? > > + TP_STRUCT__entry( > > + __field(unsigned long, pfn) Btw., does pfn always fit into 32 bits on 32-bit platforms? > > + __field(unsigned long, count) Does this have to be 64-bit on 64-bit platforms? > > + ), > > + > > + TP_fast_assign( > > + __entry->pfn = pfn; > > + __entry->count = count; > > + ), > > + > > + TP_printk("pfn=%lu page=%p count=%lu", > > + __entry->pfn, > > + pfn_to_page(__entry->pfn), > > + __entry->count) So here you print more in the TP_printk() line than in the fast-assign side. Again I'd double check the various boundary conditions. Thanks, Ingo