linux-kernel - Re: [PATCH v4 2/5] PCI: iproc: Add PAXC interface support

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]

Message-ID: <3529525.ts0Jjxrtm5@wuerfel>
Date:	Fri, 27 Nov 2015 22:11:15 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Ray Jui <rjui@...adcom.com>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	Marc Zyngier <marc.zyngier@....com>,
	Hauke Mehrtens <hauke@...ke-m.de>,
	linux-kernel@...r.kernel.org,
	bcm-kernel-feedback-list@...adcom.com, linux-pci@...r.kernel.org
Subject: Re: [PATCH v4 2/5] PCI: iproc: Add PAXC interface support

On Friday 27 November 2015 12:56:05 Ray Jui wrote:
> >
> > You seem to only need the identifiers in order to set a single
> > pointer, so just point to that array directly.
> 
> Not just a single pointer. This sets the iProc PCIe interface type, 
> which is an enum. Based on the interface type, both the iProc PCIe core 
> driver and the iProc PCIe MSI driver can 1) load the correct set of 
> register offsets; 2) skip/invoke some of the link detection, controller 
> reset related behaviors; 3) setting up the correct number of MSI event 
> queue regions and MSI address regions.

Ok, fair enough. I had missed 2) and 3) here. It could still be done
as a structure (rather than function pointers) with individual named
members for each register offset along with bool flags for 2) and
integers to describe 3).

Please that suggestion some thought, and then decide for yourself,
I won't complain if you keep the current version.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/