From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Kohli, Gaurav" <gkohli@codeaurora.org>
Subject: Query: Notifier support for callback profiling
Date: Fri, 19 May 2017 19:01:34 +0530
Message-ID: <8738660c-a644-6f9f-4da4-1d3349c3f9ea@codeaurora.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <linux-arm-msm-owner@vger.kernel.org>
Received: from smtp.codeaurora.org ([198.145.29.96]:58996 "EHLO
        smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750768AbdESNbn (ORCPT
        <rfc822;linux-arm-msm@vger.kernel.org>);
        Fri, 19 May 2017 09:31:43 -0400
Content-Language: en-US
Sender: linux-arm-msm-owner@vger.kernel.org
List-Id: linux-arm-msm@vger.kernel.org
To: linux-kernel@vger.kernel.o, linux-arm-msm@vger.kernel.org

Hi ,

Can we profile driver specific notifier callback from Linux notifier.
Sometimes we need to debug which callback is taking more time or where 
it is stuck.
If kernel/notifier.c provide generic mechanism to profile callbacks that 
will
save profiling individual callbacks.

-- 
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.