Re: [PATCH 1/2] lpfc: support for CPU phys_id and core_id on PowerPC64

2016-06-22 Thread Mauricio Faria de Oliveira
Hi Martin, On 06/21/2016 11:16 PM, Martin K. Petersen wrote: Distros are free to carry a patch such as yours. That puts the burden on them and not on upstream which is going in a different direction as outlined by Christoph. This is ultimately Broadcom's decision. It is their driver. Right,

Re: [PATCH 1/2] lpfc: support for CPU phys_id and core_id on PowerPC64

2016-06-21 Thread Martin K. Petersen
> "Mauricio" == Mauricio Faria de Oliveira > writes: Mauricio, Mauricio> This turns out to still be the case w/ some distros where Mauricio> ppc64/le usually runs, Distros are free to carry a patch such as yours. That puts the burden on them and not on upstream which is going in a diff

Re: [PATCH 1/2] lpfc: support for CPU phys_id and core_id on PowerPC64

2016-06-21 Thread Mauricio Faria de Oliveira
On 06/21/2016 11:29 AM, Christoph Hellwig wrote: I really don't think this sort of low level information has business in a low level driver. I've been trying to put some infrastructure together to move this to the core kernel [1], and it would be good to help use this in more drivers. Especiall

Re: [PATCH 1/2] lpfc: support for CPU phys_id and core_id on PowerPC64

2016-06-21 Thread Christoph Hellwig
I really don't think this sort of low level information has business in a low level driver. I've been trying to put some infrastructure together to move this to the core kernel [1], and it would be good to help use this in more drivers. Especially given that lpfc may use blk-mq which will not res

[PATCH 1/2] lpfc: support for CPU phys_id and core_id on PowerPC64

2016-06-01 Thread Mauricio Faria de Oliveira
This commit uses the macros 'topology_physical_package_id' and 'topology_core_id' from , which are defined in arch/powerpc/include/asm/topology.h for CONFIG_PPC64 && CONFIG_SMP. Also, change the initial value for min_phys_id from 0xff to INT_MAX (the numbers may increment with large steps on some