From: Philippe Gerum <rpm@xenomai.org>
To: A C <adrien_chiron@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Porting Adeos-Ipipe on AVR32 (NGW 100).
Date: Thu, 10 Dec 2009 19:11:22 +0100 [thread overview]
Message-ID: <1260468682.2370.100.camel@domain.hid> (raw)
In-Reply-To: <500245.60842.qm@domain.hid>
On Thu, 2009-12-10 at 16:48 +0000, A C wrote:
> Hello,
>
> We started to port Adeos for the IRQs part.
>
> Simple question: Why the function raw_irqs_disabled_flags(flags) is
> the same with or without ipipe ? (as we saw in some arch).
>
Because the pipeline code must guarantee that, for all standard linux
IRQ state accessors/modifiers (e.g. local_irq_save/restore(),
raw_irqs_disabled_flags()) the same values are used to assert/test the
interrupt on/off states (e.g. MSR_EE, X86_EFLAGS_IF and so on), in the
virtualized IRQ flags, than the real IRQ flags linux uses when the
pipeline is disabled, for any given arch.
e.g. on x86, albeit ugly, it must be allowed to open-code:
raw_local_save_flags(flags);
if (flags & X86_EFLAGS_IF)
interrupts_are_enabled();
even if the pipeline is enabled.
> (in the case with ipipe)
> Why not use __ipipe_test_root() -in the same way as the function
> __raw_local_save_flags()- to write the new function
> raw_irqs_disabled_flags(flags)?
Because this would break the above rule, since __ipipe_test_root()
returns 0/1.
>
> Regards
>
> Adrien Chiron & Vincent Vanbesien
>
> _______________________________________________
> Adeos-main mailing list
> Adeos-main@domain.hid
> https://mail.gna.org/listinfo/adeos-main
--
Philippe.
prev parent reply other threads:[~2009-12-10 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 16:48 [Adeos-main] Porting Adeos-Ipipe on AVR32 (NGW 100) A C
2009-12-10 18:11 ` Philippe Gerum [this message]
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=1260468682.2370.100.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=adrien_chiron@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.