Re: Merging the Suspend2 freezer implementation.

[Pavel Machek]

Hi!

> I'm keen to see if we can merge Suspend2's freezer implementation after
> 2.6.11. Does that conflict with any of your intended changes? If it
> doesn't, I'll submit a patch for review/merge as quickly as I can.

Freezer is very independend, and no, I do not plan any changes in that area.

> The main change involves the introduction of a new SYNCTHREAD flag. We
> use this to avoid deadlocking over processes that are running sys_sync
> and siblings. Processes that enter those routines get the flag added,
> and it's removed when they exit the sync routine. We then freeze in four
> stages: 

Is SYNCTHREAD neccessary for me, too, or is it needed for suspend2, only?

> 1) Freeze user space threads without SYNCTHREAD set;
> 2) Freeze user space threads with SYNCTHREAD set;
> 3) Run our own sys_sync in case no one else was syncing
> 4) Freeze kernel space threads without NOFREEZE set.
> 
> I'd also like to look at your SMP support and see if we can improve
> compatibility there at the same time.

Why not... But parts of smp support really need to be in assembly, and
they are not, neither in swsusp nor in suspend2...

> Finally I'd like to merge the support for freezer flags on workqueues.

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/