Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2017007ybi; Thu, 20 Jun 2019 07:48:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqxmxElbuh6HOSlSJYz52uw5IfMDVMbz9SEPiWcbEWri83saRnpM076F1v+Ae9Si+5HLByg4 X-Received: by 2002:a62:18d4:: with SMTP id 203mr1225619pfy.165.1561042106201; Thu, 20 Jun 2019 07:48:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561042106; cv=none; d=google.com; s=arc-20160816; b=0U1xJGU1KNZsryW4oh0ZODwxTNSgeffIlCT/Lrf9p1mFYca631YMxfaidkBxZoXhXj hukyAoJNkvTLFPrEu88IT+fJXQGssFJd+xlvKQSc7dIEbHeFAWIwwXxT5bXbHOunbu/E bSGzSHXn9KjOFjasMnbN6CNpzkBCqfwb21jcTXpLQ6C+GqdsZQdKu5Ibh/VZSVcN8gQJ 8cuUsDQQBJ2O4jZAPpAIH2Mwf1uRSrjqzUTEHMhEflojpbKZ/+X5/nQN41VGoUqcUzbo jeUizPWJLRZFaAxz35D6AqIoLXgQmRuA03TtKgXpAJCisjAZ9bOAhtQxVEJFwFO9Czel RMYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=WkoDRP+RpjJTzkVx/pPfzOBtWqxx+u4ZDkIpQXkuIKY=; b=IHlrQyhgcK2OkP4t+zE8wn3wqmGgDeW2b+NBPiTxHUQcGy+vTq4IrUsQHuSNL3zvld GY54JhU525r0bVVOrt9I/dHsJwPTE3fT13rKsg3chEGHagHeJrqQgHS3NgGOiCWmu3vO /kWbHM0eQ5WOXfZmdVsN8n/vz7MbNj58ZyuP/kpSLqqgn/0/9IvQ7s1hLL186ddUP5Zm JKbt0ujJL80bbgMIPFUKJVaPdJF1JnKpSjWl9mMZlVXDDNdHOuBBJxIOvFvZHFShSTks U0HS6r7XeeTJ3MD2eORjMAFPJjnwhSWxP6xFRfh0WX80xbSt6y39gpdOhbNdJoF4z4fX Johw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d10si17766382plr.307.2019.06.20.07.48.10; Thu, 20 Jun 2019 07:48:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731712AbfFTOrg (ORCPT + 99 others); Thu, 20 Jun 2019 10:47:36 -0400 Received: from mga07.intel.com ([134.134.136.100]:31936 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726649AbfFTOrg (ORCPT ); Thu, 20 Jun 2019 10:47:36 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jun 2019 07:47:35 -0700 X-IronPort-AV: E=Sophos;i="5.63,397,1557212400"; d="scan'208";a="168536316" Received: from tzanussi-mobl.amr.corp.intel.com (HELO [10.251.131.111]) ([10.251.131.111]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/AES256-SHA; 20 Jun 2019 07:47:35 -0700 Subject: Re: No invalid histogram error To: Masami Hiramatsu Cc: linux-kernel@vger.kernel.org, Steven Rostedt References: <20190620211737.993b09619af1fc58222549b4@kernel.org> From: "Zanussi, Tom" Message-ID: <27753f6a-9467-4dd0-d1b6-db75e577e693@linux.intel.com> Date: Thu, 20 Jun 2019 09:47:25 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1 MIME-Version: 1.0 In-Reply-To: <20190620211737.993b09619af1fc58222549b4@kernel.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Masami, On 6/20/2019 7:17 AM, Masami Hiramatsu wrote: > Hi Tom, > > I'm trying to use histogram on a synthetic event, but faced an odd situation. > > There is a synthetic event, which has foo and bar. > > /sys/kernel/debug/tracing # cat synthetic_events > testevent int foo; int bar > > And when I tried to add hist on trigger, both foo and bar can be used as below. > > /sys/kernel/debug/tracing # echo "hist:keys=bar" > events/synthetic/testevent/trigger > /sys/kernel/debug/tracing # echo "hist:keys=foo" > events/synthetic/testevent/trigger > > And, when I missed to specify the sort key, it failed > > /sys/kernel/debug/tracing # echo "hist:keys=foo:sort=bar" > events/synthetic/testevent/trigger > sh: write error: Invalid argument > > But no error on error_log file. > > /sys/kernel/debug/tracing # cat error_log > /sys/kernel/debug/tracing # > > Could you add some error message? What about below? > > [ 5422.134656] hist:synthetic:testevent: error: Sort key must be one of keys. > Command: keys=foo;sort=bar > ^ Sure, I'll submit a fix for this.  Thanks for pointing it out. Tom > Thank you, > >