Messages in this thread |  | | | Date | Wed, 26 May 2010 13:29:00 +0300 | | Subject | Re: [PATCH 1/8] PM: Opportunistic suspend support. | | From | Pekka Enberg <> |
| |
On Wed, 2010-05-26 at 03:17 -0700, Arve Hjønnevåg wrote: >> > With a single suspend manager process that manages the suspend state you >> > can achieve the same goal. >> >> Yes we don't need the /dev interface, but it is useful. Without it any >> program that needs to block suspend has to make a blocking ipc call >> into the suspend manager process. Android already does this for java >> code, but system processes written in C block suspend directly with >> the kernel since they cannot use the java APIs.
2010/5/26 Peter Zijlstra <peterz@infradead.org>: > So provide a C interface to it as well? > > Surely you can have the java thing have a unix socket or something a C > app can talk to. That shouldn't be hard at all. > > Or make the suspend manager a C proglet and provide a JNI interface, or > whatever.
Yup, I don't quite get Arve's argument either. C code can interact with Java code (and vice versa) just fine in userspace. -- 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/
|  |