From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89BA6C001B0 for ; Thu, 13 Jul 2023 23:10:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234411AbjGMXK2 (ORCPT ); Thu, 13 Jul 2023 19:10:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53154 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234410AbjGMXKZ (ORCPT ); Thu, 13 Jul 2023 19:10:25 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 59FEA1FEE for ; Thu, 13 Jul 2023 16:10:23 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id E885161B45 for ; Thu, 13 Jul 2023 23:10:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 49F04C433C7; Thu, 13 Jul 2023 23:10:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1689289822; bh=BDg3M8vA3quRdTE6TXWmhbipnn7q2n/R0hfhXMmvExg=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=f73RMbHVPq+Nol39XEeExcERjZWm9KN+lOeZLLSPLuymvP1LXptPS1A0qPqnyBDrZ 9pifTPQ7kAri66NjcShlA1lkTjQFR4qkaBwuw3oM01Ebhct7RIt8wUqJI0wnpSXKqd /7aeXPRR25vqaQ0OzI/2NyY1XAcjkXVapFhDstSnCZiiJeoSG8a8DkYetNnXC4/3jB S9QbgPg0qT8jMomUwhiJ6vHcNjk134JH68lVMJiKdM2MGYP375tvPPr3J584RQb9gn csNY+Q9Y+ygBjYsRSTsnHgdYO2LCQpU+zmGw5HBTPmtm4/EtF8WI8PVXop3YnCv+E1 /xKGISuzY1TIg== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id 30828E4508F; Thu, 13 Jul 2023 23:10:22 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH bpf-next v10 0/3] bpf, x86: allow function arguments up to 12 for TRACING From: patchwork-bot+netdevbpf@kernel.org Message-Id: <168928982219.26100.14061536595733832009.git-patchwork-notify@kernel.org> Date: Thu, 13 Jul 2023 23:10:22 +0000 References: <20230713040738.1789742-1-imagedong@tencent.com> In-Reply-To: <20230713040738.1789742-1-imagedong@tencent.com> To: Menglong Dong Cc: yhs@meta.com, daniel@iogearbox.net, alexei.starovoitov@gmail.com, ast@kernel.org, andrii@kernel.org, martin.lau@linux.dev, song@kernel.org, yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com, haoluo@google.com, dsahern@kernel.org, jolsa@kernel.org, x86@kernel.org, bpf@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, imagedong@tencent.com Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello: This series was applied to bpf/bpf-next.git (master) by Alexei Starovoitov : On Thu, 13 Jul 2023 12:07:35 +0800 you wrote: > From: Menglong Dong > > For now, the BPF program of type BPF_PROG_TYPE_TRACING can only be used > on the kernel functions whose arguments count less than or equal to 6, if > not considering '> 8 bytes' struct argument. This is not friendly at all, > as too many functions have arguments count more than 6. According to the > current kernel version, below is a statistics of the function arguments > count: > > [...] Here is the summary with links: - [bpf-next,v10,1/3] bpf, x86: save/restore regs with BPF_DW size https://git.kernel.org/bpf/bpf-next/c/02a6dfa8ff43 - [bpf-next,v10,2/3] bpf, x86: allow function arguments up to 12 for TRACING https://git.kernel.org/bpf/bpf-next/c/473e3150e30a - [bpf-next,v10,3/3] selftests/bpf: add testcase for TRACING with 6+ arguments https://git.kernel.org/bpf/bpf-next/c/5e9cf77d81f9 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html