It's a developer extra - if you're debugging stuff that runs on multiple threads, you can disable all cores but one to force stuff to run if not serially, then at least not strictly concurrently. (Of course, you can do this in code as well, even to the point of 'pinning' some code to a specific core.) There's probably a bunch of other uses for it if you're doing hardware-related development, like device drivers, but I'm not sure since I don't do that.

You can change the number of active processor cores at any time. It's not a set-and-then-restart sort of thing.

[ Reply to This | # ]