On Mon, 24 Nov 2014, David Miller wrote: > From: [email protected] > Date: Tue, 25 Nov 2014 00:23:20 +0200 (EET) > > >> > > > Yes, that does look like the case. Do you have a good trick on how > >> > > > to allocate a map for the highest possible cpu number without first > >> > > > iterating the cpu map? I couldn't find something that looks like a > >> > > > highest_possible_cpu() helper. > >> > > > >> > > Honestly I think that num_posible_cpus() should return the max of > >> > > number of CPUs (weigt), and the highest numbered CPU. It's a pain in > >> > > the butt to handle this otherwise. > >> > > >> > Hear, hear!!! That would make my life easier, and would make this sort > >> > of problem much less likely to occur! > >> > >> How about this one? > > > > It make the machine work. > > Thanks for testing! >
What's the status of this fix? It is still not applied on yesterdays 3.19.0-rc6-00105-gc59c961 git... -- Meelis Roos ([email protected]) -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
