On 07/04/2014 23:13, Dave Hylands wrote: > Personally, I think that the more ways we can test for threading issues the > better. > It seems to me that we should do some amount of testing on single core and > multi-core. > > Then I suppose the question becomes how many cores? 2? 4? 8? > > Maybe we can cycle through some different number of cores so that we get > coverage without duplicating everything?
One configuration that is particularly good at catching threading errors (especially narrow races) is constraining the software to run on two hardware threads on the same SMT-enabled core. This effectively forces the threads to share the L1 D$ which in turn can reveal some otherwise very-hard-to-find data synchronization issues. I don't know if we have that level of control on our testing hardware but if we do then that's a scenario we might want to include. Gabriele
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
