#3001: SMP build of RTEMS Testsuite does not set CONFIGURE_MAXIMUM_PROCESSORS -------------------------+------------------------------ Reporter: Chris Johns | Owner: joel.sherrill@… Type: defect | Status: new Priority: high | Milestone: 4.12.0 Component: SMP | Version: 4.12 Severity: blocker | Resolution: Keywords: | -------------------------+------------------------------ Description changed by Chris Johns:
Old description: > The default setting for {{{CONFIGURE_MAXIMUM_PROCESSORS}}} is {{{1}}} and > this means {{{rtems_configuration_is_smp_enabled()}}} returns > {{{false}}}. Only the {{{smptests}}} set the the maximum processor count > {{{CPU_COUNT}}} and therefore run in SMP mode. > > If SMP is not running in an SMP build when running the tests are the > tests really reporting a true indication of the of the system? > > I would expect we have the API tests, {{{libtests}}} and {{{fstests}}} > running with SMP enabled in an SMP build. New description: The default setting for {{{CONFIGURE_MAXIMUM_PROCESSORS}}} is {{{1}}} and this means {{{rtems_configuration_is_smp_enabled()}}} returns {{{false}}}. Only the {{{smptests}}} set the maximum processor count to {{{CPU_COUNT}}} and therefore run in SMP mode. If SMP is not running in an SMP build when running the tests are the tests really reporting a true indication of the of the system? I would expect we have the API tests, {{{libtests}}} and {{{fstests}}} running with SMP enabled in an SMP build. -- -- Ticket URL: <http://devel.rtems.org/ticket/3001#comment:1> RTEMS Project <http://www.rtems.org/> RTEMS Project
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs