Re: Getting rid of freezer for suspend [was Re: [fuse-devel] [PATCH]fuse: make fuse daemon frozen along with kernel threads]
From: Miklos Szeredi
Date: Thu Feb 14 2013 - 08:09:58 EST
On Thu, Feb 14, 2013 at 1:11 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote:
> On Thursday, February 14, 2013 11:41:16 AM Miklos Szeredi wrote:
>> It is essentially the same mechanism that is used to delay the
>> freezing of kernel threads after userspace tasks have been frozen.
>> Except it's a lot more difficult to determine which userspace tasks
>> need to be suspended late and which aren't.
> Well, I suppose that information is available to user space.
> Do we need an interface for a process to mark itself as PF_FREEZE_LATE or
> do we need an interface for one process to mark another process as
> PF_FREEZE_LATE, or both?
As a first step marking self with PF_FREEZE_LATE and inheriting this
flag across fork/clone would work for most cases, I think.
Marking an unrelated process would have all sorts of issues: Who has
permission to do this? Won't it be misused to "fix" random freezer
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/