Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936466AbcLOOdi (ORCPT ); Thu, 15 Dec 2016 09:33:38 -0500 Received: from mail.kernel.org ([198.145.29.136]:35598 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752706AbcLOOdh (ORCPT ); Thu, 15 Dec 2016 09:33:37 -0500 Date: Thu, 15 Dec 2016 11:33:29 -0300 From: Arnaldo Carvalho de Melo To: Joe Stringer Cc: Daniel Borkmann , LKML , netdev , Wang Nan , ast@fb.com Subject: Re: [PATCHv3 perf/core 0/7] Reuse libbpf from samples/bpf Message-ID: <20161215143329.GB6866@kernel.org> References: <20161209024620.31660-1-joe@ovn.org> <20161209150907.GM8257@kernel.org> <584ACE2E.2090108@iogearbox.net> <20161214132501.GP5482@kernel.org> <20161214145512.GQ5482@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1461 Lines: 33 Em Wed, Dec 14, 2016 at 02:46:23PM -0800, Joe Stringer escreveu: > On 14 December 2016 at 06:55, Arnaldo Carvalho de Melo wrote: > > So, Joe, can you try refreshing this work, starting from what I have in > > perf/core? It has the changes coming from net-next that Daniel warned us about > > and some more. > I've just respun this series based on the version you previously > applied to perf/core. Since bpf_prog_{attach,detach}() were added to > samples/libbpf, a new patch will shift these over to tools/lib/bpf. > Other than that, I folded "samples/bpf: Drop unnecessary build > targets." back into "samples/bpf: Switch over to libbpf", and I > noticed that there were a couple of unnecessary log buffers with the > latest changes. For any new sample programs, those were fixed up to > use libbpf as well. > Don't forget to do a "make headers_install" before attempting to build > the samples, access to the latest headers is required (as per the > readme in samples/bpf). Ah, README, I should read that ;-) I got used to how tools/perf/ work, i.e. it is self sufficient wrt in-flux stuff in the kernel, i.e. headers that are related to features it supports and that are under constant improvements, such as eBPF, kvm, syscall tables, etc. Anyway, will do the headers_install step inside a container, to avoid polluting my workstation. Thanks for doing the respin and for the clarifications about building samples/bpf/. - Arnaldo