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 B3DDFEB64D7 for ; Tue, 20 Jun 2023 15:32:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233544AbjFTPcs (ORCPT ); Tue, 20 Jun 2023 11:32:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56126 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231945AbjFTPcr (ORCPT ); Tue, 20 Jun 2023 11:32:47 -0400 Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4B49C186; Tue, 20 Jun 2023 08:32:46 -0700 (PDT) Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-5186a157b85so6726562a12.0; Tue, 20 Jun 2023 08:32:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687275165; x=1689867165; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=P0jVFIWxWqZ/TuBplqDvmEEANKo26b83Dz5MygWHhzo=; b=R2BhcgahF4eA1vnlN0qyJmASSGyaKyq8k8oOrUAtCf6A4nOmgevBEhPzEV8rIbjTgF yXzVElUQYcMdeYQTQkO+X2Y+9ZuwgkppnVdZSXyRsEkPbs6x/ssnctoQke0QTIMErPf3 qLgAPk3+Vpo3W0G2QiGZq35LggwDfRrpFYUUYGCVB1g7szVQ79eBlKEygcj7p7OVjxQf pa51oJokqPD+3D2MoPj8cm17qxZzYmsGb5TOKjwNPuJs0U4g/8S2QCH5/u+vSkwhFWvm 3m8n5V/yFyRQTrN52yzRlNSqLm1w2gZ7QUzER3KDhhogdRbdvNc25JV4yGkEnTVq2UW0 ShAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687275165; x=1689867165; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=P0jVFIWxWqZ/TuBplqDvmEEANKo26b83Dz5MygWHhzo=; b=XS2HZDXys8QaRBHr+MImx1H5MzU9FyVaONq+gPKBJvkypyXU/vBxA0/GeRIr2FnRCL W7SWmbfRZJreWd71BT5PHLOQp9B3W7uEW6ZthYgscyaifrV9dSYqf2yGToWc0q5afq4W w+2/oirKs2srAlLQcj2n7YRTTSk/r7d0mWsshc76/H8dGrSVIcjIp+DWteirPnsE+l1Z EH8xXhpamEgG9BcKPb2NmmJJZnQtwBBU1gjm9uu287ERcnYe+mXuAUX5p63VWvuIHesl xVcC1Y17+bneyPS2ewkN4e0xkVlQ1XUvhc4NFl7C/pbP9+T/PWWcHhlwFxLmenRmJPLu 0I6Q== X-Gm-Message-State: AC+VfDwp0VBv8JoND5a7qw1QUc1/XgKqldfKBeZgmw2CaobiuBO/mbdl Wr48MLFVqbZaBJK9bSWgd6scnfvJgltCAHsNxac= X-Google-Smtp-Source: ACHHUZ5ux98lA0dfOqVXfQP0ndlYyBoHuqHpCIjpPqNu3qgP8TLa7JJDdMIHBmrGJ6oD7j3SfcbrFl7+8TyeQPspzGA= X-Received: by 2002:aa7:cf16:0:b0:51a:40ca:d081 with SMTP id a22-20020aa7cf16000000b0051a40cad081mr7305340edy.27.1687275164525; Tue, 20 Jun 2023 08:32:44 -0700 (PDT) MIME-Version: 1.0 References: <20230616085038.4121892-1-rppt@kernel.org> <20230616085038.4121892-7-rppt@kernel.org> <87jzw0qu3s.ffs@tglx> <20230618231431.4aj3k5ujye22sqai@moria.home.lan> <87h6r4qo1d.ffs@tglx> <20230620105104.60cb64d8@gandalf.local.home> In-Reply-To: <20230620105104.60cb64d8@gandalf.local.home> From: Alexei Starovoitov Date: Tue, 20 Jun 2023 08:32:33 -0700 Message-ID: Subject: Re: [PATCH v2 06/12] mm/execmem: introduce execmem_data_alloc() To: Steven Rostedt Cc: Thomas Gleixner , Kent Overstreet , Mike Rapoport , LKML , Andrew Morton , Catalin Marinas , Christophe Leroy , "David S. Miller" , Dinh Nguyen , Heiko Carstens , Helge Deller , Huacai Chen , Luis Chamberlain , Mark Rutland , Michael Ellerman , Nadav Amit , "Naveen N. Rao" , Palmer Dabbelt , Puranjay Mohan , Rick Edgecombe , Russell King , Song Liu , Thomas Bogendoerfer , Will Deacon , bpf , linux-arm-kernel , linux-mips@vger.kernel.org, linux-mm , linux-modules@vger.kernel.org, linux-parisc@vger.kernel.org, linux-riscv , linux-s390 , linux-trace-kernel@vger.kernel.org, ppc-dev , loongarch@lists.linux.dev, Network Development , sparclinux@vger.kernel.org, X86 ML Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-mips@vger.kernel.org On Tue, Jun 20, 2023 at 7:51=E2=80=AFAM Steven Rostedt wrote: > > On Mon, 19 Jun 2023 02:43:58 +0200 > Thomas Gleixner wrote: > > > Now you might argue that it _is_ a "hotpath" due to the BPF usage, but > > then even more so as any intermediate wrapper which converts from one > > data representation to another data representation is not going to > > increase performance, right? > > Just as a side note. BPF can not attach its return calling code to > functions that have more than 6 parameters (3 on 32 bit x86), because of > the way BPF return path trampoline works. It is a requirement that all > parameters live in registers, and none on the stack. It's actually 7 and that restriction is being lifted. The patch set to attach to <=3D 12 is being discussed.