From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422663AbbEUTiI (ORCPT ); Thu, 21 May 2015 15:38:08 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:42592 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161017AbbEUTh5 (ORCPT ); Thu, 21 May 2015 15:37:57 -0400 Message-ID: <555E3413.1020201@codeaurora.org> Date: Thu, 21 May 2015 12:37:55 -0700 From: Stephen Boyd User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Steven Rostedt CC: Ankit Gupta , gavidov@codeaurora.org, sdharia@codeaurora.org, mlocke@codeaurora.org, linux-arm-msm@vger.kernel.org, gregkh@linuxfoundation.org, ivan.ivanov@linaro.org, linux-kernel@vger.kernel.org, svarbanov@mm-sol.com, galak@codeaurora.org, agross@codeaurora.org Subject: Re: [PATCH] spmi: add command tracepoints for SPMI References: <1431985887-23379-1-git-send-email-ankgupta@codeaurora.org> <555BD719.80508@codeaurora.org> <20150520090808.36cf77c2@ankgupta-lnx.qualcomm.com> <20150520182955.GR31753@codeaurora.org> <20150520145807.63f62ca7@gandalf.local.home> In-Reply-To: <20150520145807.63f62ca7@gandalf.local.home> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/20/15 11:58, Steven Rostedt wrote: > On Wed, 20 May 2015 11:29:55 -0700 > Stephen Boyd wrote: > > >>> I see no reason to spend to 4-8 bytes when spmi spec allows for maximum >>> buffer size of 16. Do you suggest changing the API of read_cmd()? >> Is that a maximum buffer size of 16 bytes? I'd prefer consistency >> with the API that's being traced, that's all. Changing it to u8 >> to save a few bytes probably doesn't make any difference if the >> architecture passes function arguments in CPU registers which are >> 32 or 64 bits wide or if the function can be inlined enough by >> the compiler to where the len parameter is kept in a register. >> > > I believe the worry is about wasting bytes in the ring buffer if not > necessary. But we do that in other tracepoints, so it's really up to > the maintainer. Ah ok. Fair enough. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project