All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Mayer <h.mayer@domain.hid>
To: Alexis Berlemont <berlemont.hauw@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] wake_up_interruptible ?
Date: Tue, 24 Jan 2006 22:16:26 +0100	[thread overview]
Message-ID: <43D6992A.60505@domain.hid> (raw)
In-Reply-To: <200601242146.35114.berlemont.hauw@domain.hid>

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.





  reply	other threads:[~2006-01-24 21:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21 22:44 [Adeos-main] wake_up_interruptible ? Hannes Mayer
2006-01-23  0:44 ` Alexis Berlemont
2006-01-23 10:56   ` Gilles Chanteperdrix
2006-01-24 17:08     ` Hannes Mayer
2006-01-24 19:23       ` Hannes Mayer
2006-01-24 20:46         ` Alexis Berlemont
2006-01-24 21:16           ` Hannes Mayer [this message]
2006-01-27 16:44             ` Hannes Mayer
2006-01-29 10:50               ` Philippe Gerum
2006-01-30 13:48                 ` Hannes Mayer
2006-01-24 21:08         ` Gilles Chanteperdrix
2006-01-24 21:20           ` Hannes Mayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43D6992A.60505@domain.hid \
    --to=h.mayer@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=berlemont.hauw@domain.hid \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.