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 X-Spam-Level: X-Spam-Status: No, score=-3.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8DCF0C169C4 for ; Wed, 6 Feb 2019 03:36:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 56E2D2184E for ; Wed, 6 Feb 2019 03:36:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="WR0XIpIL" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726547AbfBFDgF (ORCPT ); Tue, 5 Feb 2019 22:36:05 -0500 Received: from mail-pl1-f174.google.com ([209.85.214.174]:40019 "EHLO mail-pl1-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726062AbfBFDgF (ORCPT ); Tue, 5 Feb 2019 22:36:05 -0500 Received: by mail-pl1-f174.google.com with SMTP id u18so2475466plq.7 for ; Tue, 05 Feb 2019 19:36:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=cKFkU6Dh8JW89Z1eoUAWgecVhMTDW8ewRqtzhZD1S+w=; b=WR0XIpILZU16g5QNjuNLoCOhWCjUnKdn/gDsEBiOVlO/v/nhTlGXuWcOe4UroBSPG9 2BO20bV3QHD6qfUz+OolFUwbTrau3lDKir8h1vU1cUpoEe7osAwjHKYB6CZDynUelcvJ q5X77VOMgRyBypyTLlKEgxj45xhO97HIapqVWLIuwRYq8CpHli4QFp/GnuKQ70vz45Sq RZivB9u1dC6icEhjMYWZT58KHJO5zuDf3sGoq7eyzSqn0dJNnqILALnzTR8DiwN8Bz3e zx8lEDMm3T4o/cJdQodYiNuJb30yfE7y6EAximnX1nOSEtxAhktuqpwVRs5/y+3ApbKF SDGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=cKFkU6Dh8JW89Z1eoUAWgecVhMTDW8ewRqtzhZD1S+w=; b=auCeEcOr/afntBnbD51YmO2VTuYw99CjhOUy8hhTuc2K2AN7Wlm5yeOrYMWhwRjaZk JKxCxRkztG+G8TGh3V04f+kyFFiZ+4rLRlUpP/W+C8GjFvWU6ckK3gnYq+DmX7tLmq4z 2SqvfjzzNn+8eJP5ya6jyBUV9dI+XSywqPkgJblmAXiQ3Zn6Gi3s0SC/am6wEjSB2TUP YHQIWxmZ9+bt9cTDsG/a7QnZiaDKjAP7RNLbuJgsjkPjBeIvYXyh3YYt8DvmN2HGgY4C UCTgFu9uWO6VpfocLQmx5xlpk98dsqoZCdYbD4cxQWVWhOsWSKnCu/YfatF+7epyNgbO Pkkw== X-Gm-Message-State: AHQUAuYr0a3lNi9Nsn7Ym76pK4N16mNAxyA108ysvo2qxn3y4W7H25xO g89qlvlC/FJTKjxfkOHZJQY= X-Google-Smtp-Source: AHgI3IYpQxbzaHmQzSZvhStRdvQ57bRps5/DLb3Sn5at5Kn8Nb0a1pEHmTLE5l8MHH6kSlcP8UvciQ== X-Received: by 2002:a17:902:b494:: with SMTP id y20mr8716191plr.178.1549424164456; Tue, 05 Feb 2019 19:36:04 -0800 (PST) Received: from ast-mbp ([2620:10d:c090:180::1:f6ef]) by smtp.gmail.com with ESMTPSA id r4sm5896604pgn.54.2019.02.05.19.36.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Feb 2019 19:36:03 -0800 (PST) Date: Tue, 5 Feb 2019 19:36:02 -0800 From: Alexei Starovoitov To: Song Liu Cc: Daniel Borkmann , Alexei Starovoitov , Kernel Team , Netdev Subject: Re: Pull patches from tip/perf/core to bpf-next Message-ID: <20190206033600.6terh4xgozy5r3hs@ast-mbp> References: <545C47EB-4D9A-46A5-892B-D4DDB88AFFDD@fb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <545C47EB-4D9A-46A5-892B-D4DDB88AFFDD@fb.com> User-Agent: NeoMutt/20180223 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Tue, Feb 05, 2019 at 10:47:06PM +0000, Song Liu wrote: > Hi Alexei and Daniel, > > The following patches are required for BPF introspection in perf tools. > Please pull them to bpf-next, so that we get all the dependencies in one > tree. > > Thanks, > Song > > (from 1/10 to 10/10) > 76193a94522f perf, bpf: Introduce PERF_RECORD_KSYMBOL > d764ac646491 tools headers uapi: Sync tools/include/uapi/linux/perf_event.h > 6ee52e2a3fe4 perf, bpf: Introduce PERF_RECORD_BPF_EVENT > df063c83aa2c tools headers uapi: Sync tools/include/uapi/linux/perf_event.h > 9aa0bfa370b2 perf tools: Handle PERF_RECORD_KSYMBOL > 45178a928a4b perf tools: Handle PERF_RECORD_BPF_EVENT > 7b612e291a5a perf tools: Synthesize PERF_RECORD_* for loaded BPF programs > a40b95bcd30c perf top: Synthesize BPF events for pre-existing loaded BPF programs > 6934058d9fb6 bpf: Add module name [bpf] to ksymbols for bpf programs > 811184fb6977 perf bpf: Fix synthesized PERF_RECORD_KSYMBOL/BPF_EVENT yes. we can certainly do that. Do you have bpf specific patches that depend on that ? Since it's rc5 already. Are you planning to send them within next week?