Messages in this thread | | | From | Rusty Russell <> | Subject | Re: [patch 00/40] CPU hotplug rework - episode I | Date | Thu, 07 Feb 2013 14:31:04 +1030 |
| |
Thomas Gleixner <tglx@linutronix.de> writes: > On Fri, 1 Feb 2013, Linus Torvalds wrote: >> So for me it's the "expose these states" that I get worried about.. A >> random driver should not necessarily even be able to *see* this, and >> decide to be clever and take advantage of the ordering. >> >> So I'd hope there would be some visibility restrictions. We currently >> have drivers already being confused by DOWN_PREPARE vs DOWN_FAILED etc >> etc random state transitions, and giving them even more flexibility to >> pick random states sounds like a really bad idea. I'd like to make >> sure that drivers and filesystems etc do not even *see* the states >> that are meant for the scheduler or workqueues, for example).
Yeah, I assume Episode II is where we collapse each into sane states as Thomas clarified. That can be reviewed: I'd hate to try to do it in one go.
Cheers, Rusty.
| |