https://www.rtems.org/bugzilla/show_bug.cgi?id=2183
--- Comment #4 from Sebastian Huber <[email protected]> 2014-06-24 09:04:02 CDT --- (In reply to comment #3) > No. I don't think we have seen it looping infinitely. Just weird end results > where logically the scheduler wants to migrate a thread but it ends up with it > running on two processors. We are narrowing in on that and it sounds like a > completely different problem. Do you see this problem on a real RTEMS target or on the scheduler simulator? > > I was concerned because the non-affinity scheduler avoids ever moving a thread > to another core but scheduler and affinity changes result in migration of > executing threads. The migrations work quite well in general except for the problem in this bug report, see for example smptests/smpmigration02. -- Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
