[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1262446824.3058.11.camel@palomino.walls.org>
Date: Sat, 02 Jan 2010 10:40:24 -0500
From: Andy Walls <awalls@...ix.net>
To: Daniel Borkmann <danborkmann@...glemail.com>
Cc: Bartłomiej Zimoń <uzi18@...pl>,
linux-kernel@...r.kernel.org
Subject: Re: [suspend/resume] Re: userspace notification from module
On Sat, 2010-01-02 at 16:15 +0100, Daniel Borkmann wrote:
> Hi Bartłomiej,
>
> 2010/1/2 Bartłomiej Zimoń <uzi18@...pl>
> >
> > This looks like more simple and could be good, after all i think about sending this
> > module here to add to kernel. So if this solution could be ok i will start to code this part.
> >
> > Question is now what signal to choose to not terminate process and to be compatible
> > with rest of Linux kernel?
>
> Have a look at linux/signal.h. There's a section for non-POSIX
> signals. May be you
> could add a SIGSUS or sth similar into that list with a free signal
> number to stay
> compatible with the rest of the numbers.
>
> Cool thing is that you now will have a kind of "observer" principle:
> Don't call us, we call you ;)
Why not:
a. write a module that implements a device node that supports poll(),
and
b. have a user space process select() on the fd for read or exception
notification
?
Regards,
Andy
> Cheers,
> Daniel Borkmann
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists