linux-kernel - Re: [PATCH v2 2/4] PCI: Provide common functions for ECAM mapping

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, 14 Apr 2016 11:05:49 +0100
From:	Lorenzo Pieralisi <lorenzo.pieralisi@....com>
To:	Jon Masters <jcm@...masters.org>
Cc:	Catalin Marinas <catalin.marinas@....com>, rafael@...nel.org,
	linux-pci@...r.kernel.org, Will Deacon <will.deacon@....com>,
	okaya@...eaurora.org, wangyijing@...wei.com,
	Tomasz Nowicki <tn@...ihalf.com>, linaro-acpi@...ts.linaro.org,
	David Daney <ddaney@...iumnetworks.com>,
	linux-acpi@...r.kernel.org, robert.richter@...iumnetworks.com,
	Bjorn Helgaas <helgaas@...nel.org>, msalter@...hat.com,
	Arnd Bergmann <arnd@...db.de>,
	Stefano Stabellini <Stefano.Stabellini@...citrix.com>,
	Liviu.Dudau@....com, Marcin Wojtas <mw@...ihalf.com>,
	linux-arm-kernel@...ts.infradead.org,
	Jayachandran C <jchandra@...adcom.com>,
	linux-kernel@...r.kernel.org, Hanjun Guo <hanjun.guo@...aro.org>,
	Suravee.Suthikulpanit@....com, jiang.liu@...ux.intel.com
Subject: Re: [PATCH v2 2/4] PCI: Provide common functions for ECAM mapping

On Thu, Apr 14, 2016 at 01:55:32AM -0400, Jon Masters wrote:

[...]

> > I will comment on the patches as soon as I have time to review
> > them, I certainly would like to understand what we have to do with the
> > rest of the code though (provided this series is good to go) see above.
> 
> Right. That's my reason for asking. I'd like to know who is driving (I
> believe that to be Lorenzo) and what the path forward is, and whether we
> need to get additional support from anyone else. There's a multi-vendor
> meeting in the morning where I'm going to summarize the current state of
> these patches and I would like to know (soon) what the plan is so that
> we can get everyone on deck to help out at least with testing (most have
> tested the previous set, but we need public acks happening).

Testing always helps, this code needs reviewing from PCI and ACPI
standpoints, what we can do is review this series and repost the whole
thing when we agree the ECAM refactoring this series is implementing
is the right way to go and it is a step in that direction, with no
generic MCFG support in the kernel ACPI PCI on ARM64 can't be
implemented so I would start from that.

Lorenzo