From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <43D6992A.60505@domain.hid> Date: Tue, 24 Jan 2006 22:16:26 +0100 From: Hannes Mayer MIME-Version: 1.0 Subject: Re: [Adeos-main] wake_up_interruptible ? References: <43D2B94C.3000202@domain.hid> <43D65F27.7000908@domain.hid> <43D67ECD.5020309@domain.hid> <200601242146.35114.berlemont.hauw@domain.hid> In-Reply-To: <200601242146.35114.berlemont.hauw@domain.hid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: General discussion about Adeos List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexis Berlemont Cc: adeos-main@gna.org Alexis Berlemont wrote: > Hi, > > Sorry for the silly things I said earlier, forgot the most important step : > the soft irq... > >> Something like this ? >> >> inter_domain_irq = ipipe_alloc_virq(); >> ret = request_irq(inter_domain_irq, linux_handler, SA_INTERRUPT, >> "virtualIRQ", NULL); enable_irq(inter_domain_irq); >> >> void ipipe_handler(unsigned irq) { >> [...] >> ipipe_trigger_irq(inter_domain_irq); >> [...] >> } >> >> void linux_handler(void) { >> wake_up_interruptible(&skeleton_wait); >> } > > I think you should not use request_irq() but ipipe_virtualize_irq() : > > inter_domain_irq = ipipe_alloc_virq(); > -ret=request_irq(inter_domain_irq,linux_handler,SA_INTERRUPT,"virtualIRQ",NULL); > + ret = ipipe_virtualize_irq(ipipe_root_domain, > inter_domain_irq, > &ipipe_handler, > NULL, NULL, > IPIPE_HANDLE_MASK); > -enable_irq(inter_domain_irq); > > Your function linux_handler will be called in the root domain (Linux) any time > you use the function ipipe_trigger_irq(...inter_domain_irq...) in a non Linux > domain. Yes, I thought of this too. I just tried this and it works nicely. I'm just curious if the wake_up_interruptible in the new ipipe-interrupt handler (linux_handler in the above snippet) will affect HRT in any other ipipe-int-handler in the same domain ? Thank you very much and best regards, Hannes.