Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp423535ybz; Tue, 21 Apr 2020 11:40:03 -0700 (PDT) X-Google-Smtp-Source: APiQypI1XRVu7oaVHCWQQfHE1LFMibJ08Z29YNuxK9t6PvQABorR2oURRczMI1YK3TQji81tq43D X-Received: by 2002:a17:906:35cd:: with SMTP id p13mr23473382ejb.206.1587494403539; Tue, 21 Apr 2020 11:40:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587494403; cv=none; d=google.com; s=arc-20160816; b=XeEYEfv4NL/fHk6Bi5m0qc+Ffy49K9CipU2JC8KQ0Oo5elpdeVKFs81NBd0fYD3EiO Houe3qRdcduHU4FJpzEoz9JqRlQis37+mCDCLVeMhr2FfJcTP8pdQRFXTYl9PUGwYjVH saWFVG9OULrUibYyQTVmR/quhyjd9MnUaQGCkyGJsRmWrdKjWQquo87KRT7jvrzWhmYj y0ePxN1r0Goq/uXI9LhGHBrwF8KPBOzDophlpYpl5mCKzsZCcVRPrCkKyhM7zFvdPySy SO8k+NFfv/2XZgpaXrRwaMSt9I/uQQXGShCWHTPdl67t6MNISEez1sOQOiVDmQoTPg0U 8+bg== 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:organization:from:references:cc:to:subject :dkim-signature; bh=N+egMlziICIn0HZu55lHO2iyEJMLClNgk/sWJCpumsI=; b=sl9uSBUvSUlU7HfLFq+vrnn0ZG9jfFa+IaVQZVfzokatLfc8Ilm3eLz/CErQWqj5Xp VDIa3Bs3F3Bk8cRTn3fSloiEkTp75FPShfvbmQv4V+QOBRbDamC30cRNE1yQGul+YFRs PMnotWxn5ZFb0H4Ym+d3dvgnlz/mDkxxP2pWeYI0vzBP+736YSnHXG3j6eyn4I91CD/Y MVM9UamofdQLfZ8+ns2UEHx52/rLT5smq2g/pJqFBbSt0m74zL2BKB3Eqq6vVi+5Vav8 VD8ebDtdW2MfO7aW2qXv0CIx5cAA3K8BhREXXuvS61PjJnaTN9qO6GlR0JkRLPmQ8UZO pR4g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=fR+VW0xX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 34si2121750edc.238.2020.04.21.11.39.40; Tue, 21 Apr 2020 11:40:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=fR+VW0xX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729310AbgDUSgk (ORCPT + 99 others); Tue, 21 Apr 2020 14:36:40 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:59291 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725930AbgDUSgj (ORCPT ); Tue, 21 Apr 2020 14:36:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1587494198; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=N+egMlziICIn0HZu55lHO2iyEJMLClNgk/sWJCpumsI=; b=fR+VW0xXZV4EeMGa3ewMTB+q8eq9ynt6s0J4FfJl8JXAf4jksSb0N/uP1jQxxDVKpIILsY AP+2F0R/Rr3N8drHeZKO/j349USJAr954kXotP58en0zA/Hl/Da2R5HRyekrJm4ynxtWcv dlNJqCA1m/LIbwZMYzmz55bgmYaIBJk= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-79-xKU0VjHEOtivNHFtjVy3Tw-1; Tue, 21 Apr 2020 14:36:36 -0400 X-MC-Unique: xKU0VjHEOtivNHFtjVy3Tw-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A827A107ACC7; Tue, 21 Apr 2020 18:36:33 +0000 (UTC) Received: from llong.remote.csb (ovpn-114-241.rdu2.redhat.com [10.10.114.241]) by smtp.corp.redhat.com (Postfix) with ESMTP id 768595DA7C; Tue, 21 Apr 2020 18:36:29 +0000 (UTC) Subject: Re: [PATCH] blk-iocost: Fix systemtap error on iocost_ioc_vrate_adj To: Steven Rostedt Cc: Jens Axboe , Ingo Molnar , Tejun Heo , Stephen Rothwell , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, Ming Lei References: <20200421130755.18370-1-longman@redhat.com> <20200421105948.4f5a36f5@gandalf.local.home> From: Waiman Long Organization: Red Hat Message-ID: <22ccb042-7d6f-3717-4024-9ec094b2f363@redhat.com> Date: Tue, 21 Apr 2020 14:36:29 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <20200421105948.4f5a36f5@gandalf.local.home> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/21/20 10:59 AM, Steven Rostedt wrote: > On Tue, 21 Apr 2020 09:07:55 -0400 > Waiman Long wrote: > >> diff --git a/include/trace/events/iocost.h b/include/trace/events/iocost.h >> index 7ecaa65b7106..c2f580fd371b 100644 >> --- a/include/trace/events/iocost.h >> +++ b/include/trace/events/iocost.h >> @@ -130,7 +130,7 @@ DEFINE_EVENT(iocg_inuse_update, iocost_inuse_reset, >> >> TRACE_EVENT(iocost_ioc_vrate_adj, >> >> - TP_PROTO(struct ioc *ioc, u64 new_vrate, u32 (*missed_ppm)[2], >> + TP_PROTO(struct ioc *ioc, u64 new_vrate, u32 *missed_ppm, >> u32 rq_wait_pct, int nr_lagging, int nr_shortages, >> int nr_surpluses), >> >> @@ -155,8 +155,8 @@ TRACE_EVENT(iocost_ioc_vrate_adj, >> __entry->old_vrate = atomic64_read(&ioc->vtime_rate);; >> __entry->new_vrate = new_vrate; >> __entry->busy_level = ioc->busy_level; >> - __entry->read_missed_ppm = (*missed_ppm)[READ]; >> - __entry->write_missed_ppm = (*missed_ppm)[WRITE]; >> + __entry->read_missed_ppm = missed_ppm[READ]; >> + __entry->write_missed_ppm = missed_ppm[WRITE]; >> __entry->rq_wait_pct = rq_wait_pct; >> __entry->nr_lagging = nr_lagging; >> __entry->nr_shortages = nr_shortages; > Regardless if this helps systemtap or not, I like the patch because the > current code is rather ugly, and this patch makes it more readable. > > Suggestion: change the topic to remove systemtap, as that's not going to be > the true reason for acceptance of this patch. It should just be about > cleaning up the trace event itself. > > Acked-by: Steven Rostedt (VMware) > > -- Steve > OK, will send a v2 patch to update the commit log. Thanks for the review. Cheers, Longman