From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ovro.ovro.caltech.edu (ovro.ovro.caltech.edu [192.100.16.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.ovro.caltech.edu", Issuer "mail.ovro.caltech.edu" (not verified)) by ozlabs.org (Postfix) with ESMTP id 859AEDDE2E for ; Wed, 8 Aug 2007 04:32:53 +1000 (EST) Message-ID: <46B8BA93.8020909@ovro.caltech.edu> Date: Tue, 07 Aug 2007 11:31:47 -0700 From: David Hawkins MIME-Version: 1.0 To: Mirek23 Subject: Re: signals handling in the kernel References: <12032525.post@talk.nabble.com> <46B8A3C9.7060806@ovro.caltech.edu> In-Reply-To: <46B8A3C9.7060806@ovro.caltech.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Mirek, >> I would like to send signals from the interrupt handler >> routine (in the kernel) to the user application (in user space). >> I have googled on that net and I have found that it could be done with the >> function: kill_proc_info. > > Look in Rubini for the section regarding asynchronous > notification, Ch 6. > > The callback to generate SIGIO is fasync. > Actually, before you go off and implement something, can you describe why you want to use signals. I mistakenly used signals once to indicate notification of an event. Then when I wanted multiple events from multiple boards I found the problem with signals; you don't know who sent it. Using select() on multiple file descriptors ended up being a more appropriate solution for my application. That solution also works nicely with the ACE C++ ACE_Reactor pattern. Cheers, Dave