From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-174.mta0.migadu.com (out-174.mta0.migadu.com [91.218.175.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B2C2B3ECBCB for ; Tue, 20 Jan 2026 22:50:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.174 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768949416; cv=none; b=k+lX7+WBQv5FO7YMahRnTvASXmQ8I56/bJX1jGJrjavdB/HBIcF6NrN0bc1heK4JJBAdZ1ncMEcCu3eiDD5AswPTVr8hmM1EPmnVwShZ9HfH3ijQP3ZMecdOUI468dvP9YqS1wNewMWapj3OTrK7iwLg7QZsWvVxn2w8MFsFHVg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768949416; c=relaxed/simple; bh=LM9sk3nOl2uI95oAFd1Zai2C7EHFufVzGw4j1WSryVM=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=Cf08wUwZy9Dqy1dyIEnT1+0ZY5VXGPOONy2aiRXatu4YumP4YS/FkGdIY71Yr6VT93ttqEPd7YVrSObMb5cDBX79i8gOtNvCphZXuSmIPxZX343GqsNM7hRpvH7dkVjqi6H4Px0MFFQZg3RmPNHgwTEMEh7mzKJs2t0QW+m33pE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=Ziftloo4; arc=none smtp.client-ip=91.218.175.174 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="Ziftloo4" Message-ID: <7c3f053b-252b-4389-9327-e2b3f2c67c94@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1768949401; 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=LM9sk3nOl2uI95oAFd1Zai2C7EHFufVzGw4j1WSryVM=; b=Ziftloo4POu2IIFeZoTYZdsjzfR0psOkZoIi60+kfpNf6cPUxtLzCBR71ebvnUqtXiFSJC 0VJVd/lIB1IPHkKkpMCgpI6TqrZAHGpqQiuDH1b+LTtcIFKHG5J89an9yzOQnCQqhl63BF CnEqGOm7nGy6VmC5VYF2Ezu33XvTzj4= Date: Tue, 20 Jan 2026 14:49:53 -0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH bpf-next v4 1/2] bpf: support bpf_get_func_arg() for BPF_TRACE_RAW_TP Content-Language: en-GB To: Menglong Dong , ast@kernel.org, andrii@kernel.org Cc: daniel@iogearbox.net, john.fastabend@gmail.com, martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org, kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org, mattbobrowski@google.com, rostedt@goodmis.org, mhiramat@kernel.org, mathieu.desnoyers@efficios.com, bpf@vger.kernel.org, linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org References: <20260120073046.324342-1-dongml2@chinatelecom.cn> <20260120073046.324342-2-dongml2@chinatelecom.cn> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Yonghong Song In-Reply-To: <20260120073046.324342-2-dongml2@chinatelecom.cn> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 1/19/26 11:30 PM, Menglong Dong wrote: > For now, bpf_get_func_arg() and bpf_get_func_arg_cnt() is not supported by > the BPF_TRACE_RAW_TP, which is not convenient to get the argument of the > tracepoint, especially for the case that the position of the arguments in > a tracepoint can change. > > The target tracepoint BTF type id is specified during loading time, > therefore we can get the function argument count from the function > prototype instead of the stack. > > Signed-off-by: Menglong Dong Acked-by: Yonghong Song