Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752929AbbLCSgW (ORCPT ); Thu, 3 Dec 2015 13:36:22 -0500 Received: from mail-pf0-f182.google.com ([209.85.192.182]:34368 "EHLO mail-pf0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752712AbbLCSgU (ORCPT ); Thu, 3 Dec 2015 13:36:20 -0500 Message-ID: <56608BA2.2050300@linaro.org> Date: Thu, 03 Dec 2015 10:36:18 -0800 From: "Shi, Yang" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Steven Rostedt , Dave Hansen CC: akpm@linux-foundation.org, mingo@redhat.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linaro-kernel@lists.linaro.org Subject: Re: [PATCH V2 2/7] mm/gup: add gup trace points References: <1449096813-22436-1-git-send-email-yang.shi@linaro.org> <1449096813-22436-3-git-send-email-yang.shi@linaro.org> <565F8092.7000001@intel.com> <20151202231348.7058d6e2@grimm.local.home> In-Reply-To: <20151202231348.7058d6e2@grimm.local.home> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2269 Lines: 71 On 12/2/2015 8:13 PM, Steven Rostedt wrote: > On Wed, 2 Dec 2015 15:36:50 -0800 > Dave Hansen wrote: > >> On 12/02/2015 02:53 PM, Yang Shi wrote: >>> diff --git a/mm/gup.c b/mm/gup.c >>> index deafa2c..10245a4 100644 >>> --- a/mm/gup.c >>> +++ b/mm/gup.c >>> @@ -13,6 +13,9 @@ >>> #include >>> #include >>> >>> +#define CREATE_TRACE_POINTS >>> +#include >>> + >>> #include >>> #include >> >> This needs to be _the_ last thing that gets #included. Otherwise, you >> risk colliding with any other trace header that gets implicitly included >> below. > > Agreed. > >> >>> @@ -1340,6 +1346,8 @@ int __get_user_pages_fast(unsigned long start, int nr_pages, int write, >>> start, len))) >>> return 0; >>> >>> + trace_gup_get_user_pages_fast(start, nr_pages, write, pages); >>> + >>> /* >>> * Disable interrupts. We use the nested form as we can already have >>> * interrupts disabled by get_futex_key. >> >> It would be _really_ nice to be able to see return values from the >> various gup calls as well. Is that feasible? > > Only if you rewrite the functions to have a single return code path > that we can add a tracepoint too. Or have a wrapper function that gets Yes. My preliminary test just could cover the success case. gup could return errno from different a few code path. > called directly that calls these functions internally and the tracepoint > can trap the return value. This will incur more changes in other subsystems (futex, kvm, etc), I'm not sure if it is worth making such changes to get return value. > I can probably make function_graph tracer give return values, although > it will give a return value for void functions as well. And it may give > long long returns for int returns that may have bogus data in the > higher bits. If the return value requirement is not limited to gup, the approach sounds more reasonable. Thanks, Yang > > -- Steve > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/