Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp2739981pxb; Thu, 3 Feb 2022 13:12:31 -0800 (PST) X-Google-Smtp-Source: ABdhPJxt3rt626daL9NvxAcjqg63IKRp5Ieo83qON6U3a4E2pBaYFcAyNpM9TV9Tx/ktggLwKCzB X-Received: by 2002:a17:907:7f8f:: with SMTP id qk15mr26016633ejc.287.1643922751414; Thu, 03 Feb 2022 13:12:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643922751; cv=none; d=google.com; s=arc-20160816; b=EBSKeQnXxKbUZ5mGZ/S6xMwtTxpMXVdteC2jRFx6mSmzPrVVbIRMX3vL0pMrpS6YRv 7cgEfKgKMrto8NWW9jrf1DvDXEDIGGNkU1Sy4FfC43QsZ7Q0xw99hY+MrMrF2yNF0mvc XcLhe3U1kBRLCNftq3+mg6ehoZNBrmwskprfjQyJp2iRpSvH+LhPHkwvmylz7mjnzW6P FK1d+yNdKG/ajhGmnrVNHYohJHTZYNcaLHIYEHfzfz5X8IMdVj9qKAsDuHHue4BlOswf WF8lDmOiDl6CRP+EpVRZWfj7St7xnlbSzqO0x/c11u8bcD4ybqSYbgniTYEE1yYQoEay W9sw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=e8niZzxOerSalLROqW1yaPIfEQIUnjkuK5AiQtq2ICQ=; b=dpoefiePUY7d3NDI9Wbyy7FXSLgdPa1bbaoMf+nPhmomXtkx8vvXpkUBbAFOEcCvk+ IcMsIMOKgrIS22i9V22KtCrFu0ByjaMiqXJDvySfOw+QHlyDec+YwG+Qb80w7auDygjj YnAYjaE9j1eK6URtRMIT5agyOkH4hJtmKXLOf+RNPkt9B0zilzWO65H4QbXf7jDz+onp HCvrNDOElFtHAlAfdPrvrolaTkpSKwhNsM3ZdEKCHKs6uV+y/nVgKOoOSemA0TvBRdBW ZBC5J2HrLveWNNZtzDxhOzTNbqCYllFwm9SuTmvL9izcQo/7AoeiyYOn5BlkOiUZmoJL L48w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=X5oamp2c; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q11si13870614edj.298.2022.02.03.13.12.04; Thu, 03 Feb 2022 13:12:31 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=X5oamp2c; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S1351635AbiBCPGn (ORCPT + 99 others); Thu, 3 Feb 2022 10:06:43 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:25599 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237438AbiBCPGm (ORCPT ); Thu, 3 Feb 2022 10:06:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643900801; 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: in-reply-to:in-reply-to:references:references; bh=e8niZzxOerSalLROqW1yaPIfEQIUnjkuK5AiQtq2ICQ=; b=X5oamp2cmOK8WfguDT/OqzqyxmO/VyAyAPYWR4KjuOrtgRL/Qu99t5eFPeiTWobebCfMaM 0gcHj65vf5Mbz1pqTgtDB52zxkJSKs/m57lznRcC9pNSicTLyvEic4rHMtBTYa4NldJT0e nMWPDdTbseZMXSeo4Rto0G0KuinhXKI= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-640-SEnSngJ-MGSz6_Ol1ahX9Q-1; Thu, 03 Feb 2022 10:06:40 -0500 X-MC-Unique: SEnSngJ-MGSz6_Ol1ahX9Q-1 Received: by mail-wm1-f72.google.com with SMTP id r10-20020a1c440a000000b00355272f7d08so477380wma.9 for ; Thu, 03 Feb 2022 07:06:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=e8niZzxOerSalLROqW1yaPIfEQIUnjkuK5AiQtq2ICQ=; b=i1gHo+F3hWW8rDhlJYDBPwnGZEzMsUXhm2s0epLqvMHLzt5qlYJm0UhoazJX293uLu 6hdYqRLkxgeR2CCA/vEGh7nvVOxZ+WUfZlo21IyDP0s3P14rKRjQ9D+IVF2/3I2ICINF Ds16YNDhQpYF980HuoCxmsUs+vY3YdOog25ygH5beO7AXwCljMRuIho0z6F3ofw6uOu5 utsmub533OXTDqPkC0BHU7hkqnQukDC7CbrryFnEecr6XBT+YwTUqasxPpiknw5xRehk KmK/jlYTeNFJxToyJx2maoGEhdZbGrf45FKHxakE/hi6k94oGh7R06utg5NpxpoUBuVW HhpA== X-Gm-Message-State: AOAM531bV0wwEpWe5YC3ZBKvCl1UVPNdeghufrw/FQ7izVKqBThX4+bR rPZssYUU4nahCG+ghYj1m3OAnZ4RKvuUeGUOmrZ1TqhT6JDvnulCA4MBtc12Daang7TjmvoV6+b hcu17ClFRC1i+sv3sruu/P97Z X-Received: by 2002:a5d:584a:: with SMTP id i10mr29740984wrf.305.1643900799592; Thu, 03 Feb 2022 07:06:39 -0800 (PST) X-Received: by 2002:a5d:584a:: with SMTP id i10mr29740953wrf.305.1643900799362; Thu, 03 Feb 2022 07:06:39 -0800 (PST) Received: from krava (nat-pool-brq-u.redhat.com. [213.175.37.12]) by smtp.gmail.com with ESMTPSA id o10sm9478745wri.69.2022.02.03.07.06.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 03 Feb 2022 07:06:38 -0800 (PST) Date: Thu, 3 Feb 2022 16:06:36 +0100 From: Jiri Olsa To: Alexei Starovoitov Cc: Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Masami Hiramatsu , Network Development , bpf , lkml , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , Steven Rostedt , Jiri Olsa Subject: Re: [PATCH 0/8] bpf: Add fprobe link Message-ID: References: <20220202135333.190761-1-jolsa@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 02, 2022 at 09:30:21AM -0800, Alexei Starovoitov wrote: > On Wed, Feb 2, 2022 at 9:24 AM Jiri Olsa wrote: > > > > On Wed, Feb 02, 2022 at 09:09:53AM -0800, Alexei Starovoitov wrote: > > > On Wed, Feb 2, 2022 at 5:53 AM Jiri Olsa wrote: > > > > > > > > hi, > > > > this patchset adds new link type BPF_LINK_TYPE_FPROBE that attaches kprobe > > > > program through fprobe API [1] instroduced by Masami. > > > > > > No new prog type please. > > > I thought I made my reasons clear earlier. > > > It's a multi kprobe. Not a fprobe or any other name. > > > The kernel internal names should not leak into uapi. > > > > > > > well it's not new prog type, it's new link type that allows > > to attach kprobe program to multiple functions > > > > the original change used BPF_LINK_TYPE_RAW_KPROBE, which did not > > seem to fit anymore, so I moved to FPROBE, because that's what > > it is ;-) > > Now I don't like the fprobe name even more. > Why invent new names? It's an ftrace interface. how about ftrace_probe ? > > > but if you don't want new name in uapi we could make this more > > obvious with link name: > > BPF_LINK_TYPE_MULTI_KPROBE > > > > and bpf_attach_type: > > BPF_TRACE_MULTI_KPROBE > > I'd rather get rid of fprobe name first. > Masami, any idea? thanks, jirka