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:	Thu, 11 Feb 2016 01:56:43 +0700
From:	Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>
To:	Borislav Petkov <bp@...en8.de>
CC:	<joro@...tes.org>, <peterz@...radead.org>, <mingo@...hat.com>,
	<acme@...nel.org>, <andihartmann@...enet.de>,
	<linux-kernel@...r.kernel.org>, <iommu@...ts.linux-foundation.org>
Subject: Re: [PATCH V3 1/5] perf/amd/iommu: Consolidate and move
 perf_event_amd_iommu header

Hi,

On 2/11/16 01:51, Borislav Petkov wrote:
>> So, I thought it might be alright to put the perf_event_amd_iommu.h
>> >here.
>> >
>> >Having the information in the file arch/x86/events/amd/iommu.h seems
>> >strange for having to specify ../../arch/x86/events/amd/iommu.h in the
>> >IOMMU driver.
>> >
>> >So, you think it would be alright if move
>> >
>> >include/linux/perf/perf_event_amd_iommu.h
>> >to
>> >arch/x86/include/perf/perf_event_amd_iommu.h
> If it feels strange to you, you can move it to arch/x86/include/asm/
> There we put the arch-specific stuff.
>
> Then you can do
>
> #include <asm/perf/amd/iommu.h>
>
> or so. I've moved it to arch/x86/events/amd/iommu.h already anyway.

Ah.. agree then ;) So, I should branch off that tree of yours with the 
file already moved. Could you point me to it?

Thanks,
Suravee

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ