> > We could provide an "example" default implementation that does only > > swsusp that an arch can "drop in" if you want, but archs have to > > implement the various "inline" callbacks anyway (save_processor_state & > > friends). > > How could I work with that in an implementation where the vast majority > of the code is arch-independent? I guess I'll have to see what you come > up with. The arch independent code is called by the arch code, nothing new here. I don't suggest arch re-implements swsusp_suspend() or freeze_processes(). It's either that or having all the new callbacks plus a major blowup of the crap in disk.c to fit in main.c Ben.
