From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] [RFC] Consolidated exception prologue/epiloge for x86 and ARM
Date: Fri, 27 Feb 2015 21:24:53 +0100 [thread overview]
Message-ID: <20150227202453.GK434@hermes.click-hack.org> (raw)
In-Reply-To: <54F0CF9E.1040707@siemens.com>
On Fri, Feb 27, 2015 at 09:12:14PM +0100, Jan Kiszka wrote:
> Hi,
>
> just pushed a first implementation of the general model that I proposed
> for exception handling. You can find it at
>
> http://git.xenomai.org/ipipe-jki.git/log/?h=queues/trap-rework
NACK. The ARM implementation is broken, re-enabling hardware irqs
before stalling root is wrong.
Besides, I find that
if (foo) {
bar;
} else {
qux;
}
When there is nothing after adds useless indentation.
if (foo) {
bar;
return;
}
qux;
is much clearer.
Both thins were handled correctly in the implementation I proposed.
Also, reading your implementation as patches makes things uselessly
hard to read.
Simply posting the prologue and epilogue code would have made things
simpler.
>
> I can also relay the patches to the list if desired.
>
> Besides the issue that Gilles remarked, I found no further problems
> while implementing and testing this approach on both x86-64 and ARMv7.
>
> I also added support for hardware breakpoint handling on ARM at this
> chance but I didn't test that particular path yet.
As you had been warned, your tests were useless since I disagree
with your implementation.
--
Gilles.
next prev parent reply other threads:[~2015-02-27 20:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 20:12 [Xenomai] [RFC] Consolidated exception prologue/epiloge for x86 and ARM Jan Kiszka
2015-02-27 20:24 ` Gilles Chanteperdrix [this message]
2015-02-27 20:37 ` Jan Kiszka
2015-02-27 20:39 ` Gilles Chanteperdrix
2015-02-27 20:47 ` Jan Kiszka
2015-02-27 20:50 ` Gilles Chanteperdrix
2015-03-02 17:40 ` Jan Kiszka
2015-03-02 17:42 ` Gilles Chanteperdrix
2015-02-27 20:27 ` Gilles Chanteperdrix
2015-02-27 20:37 ` Jan Kiszka
2015-02-27 21:21 ` Gilles Chanteperdrix
2015-02-27 21:24 ` Gilles Chanteperdrix
2015-03-02 17:39 ` Jan Kiszka
2015-03-02 17:41 ` Gilles Chanteperdrix
2015-03-02 17:45 ` Jan Kiszka
2015-03-02 17:47 ` Gilles Chanteperdrix
2015-03-02 17:49 ` Jan Kiszka
2015-03-02 17:53 ` Gilles Chanteperdrix
2015-03-02 18:53 ` Philippe Gerum
2015-03-02 19:17 ` Jan Kiszka
2015-03-02 20:31 ` Jan Kiszka
2015-03-03 14:26 ` Philippe Gerum
2015-03-03 14:34 ` Philippe Gerum
2015-03-03 8:31 ` 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=20150227202453.GK434@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@siemens.com \
--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.