From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1762347AbcALLQn (ORCPT <rfc822;w@1wt.eu>);
	Tue, 12 Jan 2016 06:16:43 -0500
Received: from mail-wm0-f68.google.com ([74.125.82.68]:34126 "EHLO
	mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751683AbcALLQk (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 12 Jan 2016 06:16:40 -0500
Date: Tue, 12 Jan 2016 12:16:36 +0100
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, X86 ML <x86@kernel.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Arnaldo Carvalho de Melo <acme@infradead.org>,
        Jiri Olsa <jolsa@redhat.com>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC PATCH 0/5] perf: Sanitize perf directory structure, p1
Message-ID: <20160112111635.GA26496@gmail.com>
References: <1450814151-21945-1-git-send-email-bp@alien8.de>
 <20160111123944.GA13637@gmail.com>
 <20160111143439.GA4665@pd.tnic>
 <20160111151411.GC23096@gmail.com>
 <20160111163222.GB4665@pd.tnic>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160111163222.GB4665@pd.tnic>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* Borislav Petkov <bp@alien8.de> wrote:

> On Mon, Jan 11, 2016 at 04:14:12PM +0100, Ingo Molnar wrote:
> > Ok, works for me. Got confused by your ascii art:
> > 
> > arch/x86/events/
> > |-- amd
> > |   |-- core.c
> > |   |-- ibs.c
> > |   |-- iommu.c
> > |   |-- iommu.h
> > |   `-- uncore.c
> > |-- core.c
> > `-- Makefile
> > 
> > which lists events/amd/core.c.
> 
> No, that's all correct. There is an amd/core.c thing:
> 
>  arch/x86/{kernel/cpu/perf_event_amd.c => events/amd/core.c}       | 2 +-
> 
> and there's also a arch/x86/kernel/cpu/perf_event_intel.c which would want to
> become events/intel/core.c
> 
> Hmm, what do we call those then?

core.c is fine with me!

Thanks,

	Ingo