All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Jeff Weber <jweber@domain.hid>
Cc: Xenomai Help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] enable/disable all interrupts from user space
Date: Fri, 27 Oct 2006 18:24:46 +0200	[thread overview]
Message-ID: <454232CE.3010206@domain.hid> (raw)
In-Reply-To: <200610271108.14937.jweber@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

Jeff Weber wrote:
> Thanks Jan.
> 
> Another thought: is there a direct Adeos  call to enable/disable all 
> interrupts, with nesting from user space?

Not yet, but that would be one option for the scenario I described.

> 
> I'm porting some legacy RTAI code to the Xenomai native skin.  The RTAI code 
> has rtai_save_flags_and_cli()/rtai_restore_flags() for enabling/disabling all 
> interrupts  direct from user space, with capability to handle nested calls.  

You can use even more assembly magic in user-space for now:

#define local_irq_save(x) \
	__asm__ __volatile__("pushfl; popl %0; cli":"=g" (x)::"memory")

#define local_irq_restore(x) \
	__asm__ __volatile__("pushl %0; popfl": :"g" (x):"memory", "cc")

Hope your RTAI code takes care of SMP as well (or excludes the execution
on such boxes).

> 
> Yes, please add this to the native skin "wish list", along with a nesting 
> capability.

Won't you? => http://www.xenomai.org/wiki/index.php/TaskMarket

Ideas and requests on the mailing list are starting become volatile with
the increasing traffic we see...

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2006-10-27 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26 21:39 [Xenomai-help] enable/disable all interrupts from user space Jeff Weber
2006-10-27 13:32 ` Jan Kiszka
2006-10-27 16:08   ` Jeff Weber
2006-10-27 16:24     ` Jan Kiszka [this message]
2006-10-27 21:11   ` Philippe Gerum
2006-10-27 21:31     ` Jan Kiszka
2006-10-27 22:03       ` 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=454232CE.3010206@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=jweber@domain.hid \
    --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.