linux-kernel - Re: [RFC PATCH 0/5] perf: Sanitize perf directory structure, p1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 Jan 2016 17:32:23 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>, X86 ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Jiri Olsa <jolsa@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC PATCH 0/5] perf: Sanitize perf directory structure, p1

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?

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.