I can imagine some users (applications) wanting to insist on
staying on a particular CPU (Pike's Peak or Bust), and some
content to be migrated automatically, and some wanting to
receive and act on requests to migrate.
One of these policies might be default, with others as options.
Some CPU shut down operations _can't_ fail ... if they are motivated
say by hardware about to fail.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.650.933.1373- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/