Hi! > > There are many drivers that do not fit your idea of "driver". Like > > mtrrs. Some drivers only ever do work on resume, etc. Forcing driver > > to think how to split it into class->stop, bus->save_state and > > bus->enter state is bad idea. [Notice that almost no drivers need > > ->save_state operation...] > > I don't think MTRRs should be counted as drivers. Rather, they should be > counted as part of the CPU state(s), to be saved and restored when CPU > context is saved and restored. Treating them as drivers leads to races > :> Okay, I'll need to make cpu hotplug deal with them. But MTRR are not the only strange device. Think timer, for example. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
