> > To summarise, we can either have firmware handling in user space or power
> > management, but not both.
> > More philosophically speaking, IMHO we have a classical layering violation
> > caused by wishful thinking.
> > To quote Dave: "There are many good reasons to have device handling in
> > kernel space." I might add: They are sometimes less than obvious.
>
> We still could delay initializing all devices that need firmware re-load
> (or any other user space helper) until all those who don't need it are
> initalized. Anyway, as said before - recovery from a suspend is a
> dependency tree.
It is _not_ in this regard. The problem would exist with one device only.
> And then we can happily page out or read in any page or data we need
> during the firmware reload. As said before, it's up to the user not to
> create cycles in the dependency tree for example by putting the firmware
> on the firmware needing drive itself.
Once again. It does _not_ matter where the firmware resides. _Any_ dirty
page of _any_ file residing or accessed through such a device is enough.
Once we start page faults or reads or open or fork, the kernel may decide
to page out.
In fact, no user space task should run until devices involved in paging
have resumed operation. If any are running you need extra logic to make
them wait for devices which are not yet resumed.
You are complicating a core subsystem just for the sake of removing one
driver from the kernel.
Regards
Oliver
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
