All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Kalibera <kalibera@domain.hid>
To: rpm@xenomai.org
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Cannot end interrupt from user space: add	rt_intr_end call ?
Date: Thu, 24 Apr 2008 12:08:18 -0400	[thread overview]
Message-ID: <4810B072.6050603@domain.hid> (raw)
In-Reply-To: <481048A0.7040101@domain.hid>


Hi Philippe,

thank you for the patch !

> xnarch_end_irq() basically calls the ->unmask() method of the interrupt chip
> descriptor, which is the same as calling rt_intr_enable(). Before you do that,
>   
If I read the sources correctly, for "edge" and "simple" interrupt, 
xnarch_end_irq() calls nothing, for "percpu" it calls ->eoi() . For 
"level", "fasteoi", and "demux", it calls ->unmask().

So calling rt_intr_enable from user space would not always do the same 
as xnarch_end_irq from the kernel, wouldn't it ?

Tomas



Philippe Gerum wrote:
> Tomas Kalibera wrote:
>   
>> Hi,
>>
>> I think that when I handle interrupts from user space, I cannot 
>> correctly use I_NOAUTOENA. The thing is that this flag in fact means "do 
>> not call automatically xnarch_end_irq". The xnarch_end_irq call usually 
>> maps to unmasking the interrupt, but not always - depending on interrupt 
>> type (sometimes in eoi, sometimes is nop).
>>
>> I was thinking that it would be nice if I could call something like 
>> "xnarch_end_irq" (i.e. rt_intr_end) from user space, so that I could 
>> correctly use I_NOAUTOENA to control the flow of interrupts.
>>
>>     
>
> What would this buy you? xnarch_irq_end() would still handle the unmasking logic
> depending on the interrupt type, because it knows how the interrupt was
> acknowledged in the first place -- in contrast, the application does not and
> should not.
>
> xnarch_end_irq() basically calls the ->unmask() method of the interrupt chip
> descriptor, which is the same as calling rt_intr_enable(). Before you do that,
> you may want to try the attached patch, which makes sure that
> rt_intr_enable/disable are eagerly routed to unmask/mask on x86 for post-2.6.18
> kernels. That patch is expected to solve the "rt_intr_disable() not masking
> IO-APIC interrupt" issue we discussed earlier.
>
>   
>> Cheers,
>> Tomas
>>
>>
>>
>> _______________________________________________
>> Xenomai-core mailing list
>> Xenomai-core@domain.hid
>> https://mail.gna.org/listinfo/xenomai-core
>>
>>     
>
>
>   



  reply	other threads:[~2008-04-24 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24  4:33 [Xenomai-core] Cannot end interrupt from user space: add rt_intr_end call ? Tomas Kalibera
2008-04-24  8:45 ` Philippe Gerum
2008-04-24 16:08   ` Tomas Kalibera [this message]
2008-04-24 16:39     ` Philippe Gerum
2008-04-24 19:16       ` Tomas Kalibera
2008-04-25  7:12         ` Philippe Gerum

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=4810B072.6050603@domain.hid \
    --to=kalibera@domain.hid \
    --cc=rpm@xenomai.org \
    --cc=xenomai@xenomai.org \
    /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.