From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751943AbeEBQ5l (ORCPT ); Wed, 2 May 2018 12:57:41 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:46336 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751344AbeEBQ5k (ORCPT ); Wed, 2 May 2018 12:57:40 -0400 Date: Wed, 2 May 2018 18:57:37 +0200 From: Jiri Olsa To: Stephane Eranian Cc: LKML , Adrian Hunter , Arnaldo Carvalho de Melo , mingo@elte.hu, Peter Zijlstra Subject: Re: [RFC] perf record: dead code perf_event__synthesize_id_index() Message-ID: <20180502165737.GF11539@krava> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 02, 2018 at 04:38:33PM +0000, Stephane Eranian wrote: > Hi, > > It looks like perf_event__synthesize_id_index() is dead code in the current > tip > tree. I don't see any invocation of the function anywhere in perf.I > understand why > you'd want to keep the rest of the code related to PERF_RECORD_ID_INDEX > because some perf.data file may have this user-level record type. But the > synthesize code is not needed anymore, in my opinion. > > Shouldn't we remove this code? looks like there never was any user of it, probably some preparation for follow up that haven't happened yet.. Adrian? jirka