Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp1470340ybm; Tue, 21 May 2019 14:49:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqzbnGkZtZ7KkEtFsx92nEyJtGUkiE+bWLSlryC2RKelRIHu/EhZTcSCKh0B3TzFfqPcYEyO X-Received: by 2002:a63:1045:: with SMTP id 5mr41237713pgq.55.1558475377180; Tue, 21 May 2019 14:49:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558475377; cv=none; d=google.com; s=arc-20160816; b=gSvv8hg9pGl1CmRRIDKcmPRLqABkVccZFOaaOiYPZGeQybv2K0Dt41eIQkXvS0NnZv XEmhEqhHvmN/WEV7zVehN+cTFihSu534RVGm7idiU0NoJrWahBe0Lg7aCyC88lh3GYcj HKATT80MRXjMHyJHKKERKxnC08jeqjapwSmcDTuFB0Botj2eiD4vp6oZgdCM2qz+H9sG ovZ2HomDH813rJ4smMthhPIEPXnErCOCHts0aAD/FKxWDMwuIEsO5QIXY+rjuvn2qUFF YfKK8wT58KfN0kckMmEza0VpXkFY0PXSosy4Uvycv+fG0haAEfwgIe4B77eKUo6OmEAQ E+tQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=pdeNadKFfFz/Uf7DIjiAEqXdERyCJBTe2RhOiTQjpLE=; b=Gi452TvPQx0AiJvUTcJpokPaMaA1eHvWi4ZHmd6zpPc4zKEZYMqm5seFibbprRovYY B97qWpCv/qM3HDYXnWbSJtYQyyrFrECjk5Q/EemSRKTE51L7YwMsyjaZzqSgMDnSejW7 1q8B0K5m3ToSgbv8ADyr6wA21XLPLXQpRnzRkDZ7c7LzCOdC2CJ5FoeXqtXMKjr2O8Il HmJ/ustsLMODkXrzaRZhlpuT6+lGnmK4Zqkcton7fnUdxcq5yUJqqqryYIe9RSVKIt3M EbUxh0tTiI0SwdcETHDi75I8Gd5+tUHj+GANLbt23Yr8uL51f/BErgsYAp39Qv8MP0HH iO7A== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cp14si24420643plb.183.2019.05.21.14.49.21; Tue, 21 May 2019 14:49:37 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727825AbfEUVsO (ORCPT + 99 others); Tue, 21 May 2019 17:48:14 -0400 Received: from mail.kernel.org ([198.145.29.99]:60596 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726907AbfEUVsO (ORCPT ); Tue, 21 May 2019 17:48:14 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D8272217F9; Tue, 21 May 2019 21:48:12 +0000 (UTC) Date: Tue, 21 May 2019 17:48:11 -0400 From: Steven Rostedt To: Alexei Starovoitov Cc: Kris Van Hees , netdev@vger.kernel.org, bpf@vger.kernel.org, dtrace-devel@oss.oracle.com, linux-kernel@vger.kernel.org, mhiramat@kernel.org, acme@kernel.org, ast@kernel.org, daniel@iogearbox.net, peterz@infradead.org Subject: Re: [RFC PATCH 00/11] bpf, trace, dtrace: DTrace BPF program type implementation and sample use Message-ID: <20190521174757.74ec8937@gandalf.local.home> In-Reply-To: <20190521214325.rr7emn5z3b7wqiiy@ast-mbp.dhcp.thefacebook.com> References: <201905202347.x4KNl0cs030532@aserv0121.oracle.com> <20190521175617.ipry6ue7o24a2e6n@ast-mbp.dhcp.thefacebook.com> <20190521184137.GH2422@oracle.com> <20190521205533.evfszcjvdouby7vp@ast-mbp.dhcp.thefacebook.com> <20190521173618.2ebe8c1f@gandalf.local.home> <20190521214325.rr7emn5z3b7wqiiy@ast-mbp.dhcp.thefacebook.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 21 May 2019 14:43:26 -0700 Alexei Starovoitov wrote: > Steve, > sounds like you've missed all prior threads. I probably have missed them ;-) > The feedback was given to Kris it was very clear: > implement dtrace the same way as bpftrace is working with bpf. > No changes are necessary to dtrace scripts > and no kernel changes are necessary. Kris, I haven't been keeping up on all the discussions. But what exactly is the issue where Dtrace can't be done the same way as the bpftrace is done? -- Steve