Am Montag, 9. Juli 2007 schrieb Miklos Szeredi: > In that case the "we need suspend to be invisible to userspace" as a > reason to use the freezer would also be moot, since if you don't > schedule userspace after offlining the CPUs, it can't notice this. After? Can you do the offlining atomically? Regards Oliver - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway)
- From: Miklos Szeredi <miklos@szeredi.hu>
- Re: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway)
- References:
- Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: Oliver Neukum <oliver@neukum.org>
- Re: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway)
- From: "Rafael J. Wysocki" <rjw@sisk.pl>
- Re: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway)
- From: Miklos Szeredi <miklos@szeredi.hu>
- Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- Prev by Date: Re: [PATCH] Remove process freezer from suspend to RAM pathway
- Next by Date: Re: [PATCH 17/20] SMP: Implement on_cpu()
- Previous by thread: Re: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway)
- Next by thread: Re: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway)
- Index(es):
![]() |