All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] ipipe: issues with ARM exception handling
Date: Mon, 23 Feb 2015 19:32:21 +0100	[thread overview]
Message-ID: <54EB7235.4000401@siemens.com> (raw)
In-Reply-To: <54EB6E68.3010200@siemens.com>

On 2015-02-23 19:16, Jan Kiszka wrote:
> On 2015-02-23 19:11, Gilles Chanteperdrix wrote:
>> On Mon, Feb 23, 2015 at 07:04:25PM +0100, Gilles Chanteperdrix wrote:
>>> So, finally, I propose:
>>
>> Mmmm. try again.
>>
>>>
>>> static inline unsigned long ipipe_fault_entry(void)
>>> {
>>> 	unsigned long flags;
>>>
>>> 	local_irq_save(flags);      /* Re-enables hw irqs */
>>
>> We need the explicit hard_local_irq_enable() here.

And we need to fix up regs->ARM_cpsr according to flags.

>>
>>>
>>> 	return flags;
>>> }
>>>
>>> static inline void ipipe_fault_exit(unsigned long x)
>>> {
>>> 	if (irqs_disabled()) {
>>> 		__ipipe_restore_root_nosync(x);
>>> 		hard_local_irq_disable();
>>> 	}
>>> }
>>
>> We need hard_local_irq_disable() before __ipipe_restore_root_nosync,
>> to avoid the preemption of a Linux interrupt where this should not
>> be possible.
> 
> ipipe_restore_root_nosync?
> 
> But we first need to understand the differences to x86 to be sure that
> we don't miss something. The remaining differences either have to have
> an architecture-specific reason - or one side is still wrong (or
> needlessly complex).

Seems like we are converging now with the last mystery (special x86
handling on root entry) solved.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2015-02-23 18:32 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 18:03 [Xenomai] ipipe: issues with ARM exception handling Jan Kiszka
2015-02-20 18:13 ` Gilles Chanteperdrix
2015-02-20 18:17 ` Jan Kiszka
2015-02-20 18:19   ` Jan Kiszka
2015-02-20 19:44   ` Philippe Gerum
2015-02-20 19:47     ` Philippe Gerum
2015-02-20 19:52       ` Philippe Gerum
2015-02-23 16:06         ` Jan Kiszka
2015-02-23 16:32           ` Philippe Gerum
2015-02-23 16:37             ` Gilles Chanteperdrix
2015-02-23 16:50               ` Jan Kiszka
2015-02-23 16:52                 ` Gilles Chanteperdrix
2015-02-23 17:02                   ` Jan Kiszka
2015-02-23 17:14                     ` Gilles Chanteperdrix
2015-02-23 17:38                       ` Jan Kiszka
2015-02-23 17:49                         ` Jan Kiszka
2015-02-23 17:52                           ` Jan Kiszka
2015-02-23 18:30                             ` Jan Kiszka
2015-02-24 16:23                               ` Jan Kiszka
2015-02-24 16:45                                 ` Gilles Chanteperdrix
2015-02-24 16:46                                   ` Jan Kiszka
2015-02-24 16:50                                     ` Gilles Chanteperdrix
2015-02-23 16:55                 ` Gilles Chanteperdrix
2015-02-23 17:01                   ` Philippe Gerum
2015-02-23 17:12                     ` Gilles Chanteperdrix
2015-02-23 17:21                       ` Gilles Chanteperdrix
2015-02-23 17:43                         ` Jan Kiszka
2015-02-23 17:51                           ` Gilles Chanteperdrix
2015-02-23 17:54                             ` Jan Kiszka
2015-02-23 18:04                               ` Gilles Chanteperdrix
2015-02-23 18:11                                 ` Gilles Chanteperdrix
2015-02-23 18:16                                   ` Jan Kiszka
2015-02-23 18:32                                     ` Jan Kiszka [this message]
2015-02-23 18:34                                       ` Gilles Chanteperdrix
2015-02-23 19:14                                         ` Jan Kiszka
2015-02-23 19:18                                           ` Gilles Chanteperdrix
2015-02-23 18:33                                     ` Gilles Chanteperdrix
2015-02-23 19:13                                   ` Gilles Chanteperdrix
2015-02-23 20:25                       ` Philippe Gerum
2015-02-23 20:27                         ` Gilles Chanteperdrix
2015-02-23 20:33                           ` Philippe Gerum
2015-02-23 20:38                             ` Gilles Chanteperdrix
2015-02-23 20:49                               ` Philippe Gerum
2015-02-23 20:54                                 ` Gilles Chanteperdrix
2015-02-23 20:43                       ` Philippe Gerum
2015-02-23 20:46                         ` Gilles Chanteperdrix
2015-02-23 17:02                   ` Gilles Chanteperdrix
2015-02-20 18:38 ` Gilles Chanteperdrix
2015-02-20 18:51   ` Jan Kiszka
2015-02-20 18:53     ` Gilles Chanteperdrix
2015-02-20 18:57       ` Jan Kiszka
2015-02-20 18:59         ` Gilles Chanteperdrix
2015-02-20 19:04           ` Jan Kiszka
2015-02-21  9:13     ` Philippe Gerum
2015-02-23 15:59       ` Jan Kiszka
2015-02-23 16:29         ` Philippe Gerum
2015-02-23 16:58           ` Jan Kiszka

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=54EB7235.4000401@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gilles.chanteperdrix@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.