From: Jan Kiszka <jan.kiszka@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>, Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Mayday mechanism broken on x86-64 - simpler approach feasible?
Date: Thu, 12 Feb 2015 18:02:16 +0100 [thread overview]
Message-ID: <54DCDC98.5070402@siemens.com> (raw)
In-Reply-To: <54DCD68F.5020005@siemens.com>
On 2015-02-12 17:36, Jan Kiszka wrote:
>> As I mentioned earlier, I'd rather fix the MAYDAY implementation for
>> x86_64 instead of forking the implementation between MMU-enabled and
>> MMU-less architectures, also affecting powerpc, arm and x86_32 in the
>> same move. Fortunately, the current implementation allows very specific
>> tweaks to be applied on a per-architecture basis. This one fixes the
>> issue for Cobalt on x86_64, and could be easily backported to 2.6.x:
>>
>> http://git.xenomai.org/xenomai-3.git/commit/?h=next&id=6db20901963d634b9786467c711c2ba526db48a2
>
> Looks almost good - except for the detail that some bits of the
> instruction pointer are lost on return from the syscall (int vs. long
> return type). Patches in the making.
Will take longer - I need to convert all cobalt syscalls.
We have a sleeping bug there, though likely not seen in practice, with
syscalls returning values > INT_MAX (size_t...). The problem is that
handle_head/root_syscall only forwarded 32-bits so far.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2015-02-12 17:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 16:57 [Xenomai] Mayday mechanism broken on x86-64 - simpler approach feasible? Jan Kiszka
2014-12-17 17:19 ` Philippe Gerum
2014-12-17 17:17 ` Gilles Chanteperdrix
2014-12-17 17:36 ` Jan Kiszka
2014-12-17 17:45 ` Gilles Chanteperdrix
2014-12-17 17:49 ` Jan Kiszka
2014-12-17 17:37 ` Jan Kiszka
2014-12-17 17:52 ` Philippe Gerum
2014-12-17 17:46 ` Jan Kiszka
2014-12-17 18:28 ` Philippe Gerum
2014-12-17 18:32 ` Jan Kiszka
2014-12-17 18:33 ` Jan Kiszka
2014-12-17 18:55 ` Philippe Gerum
2014-12-17 18:57 ` Jan Kiszka
2015-02-03 15:29 ` Philippe Gerum
2015-02-12 16:36 ` Jan Kiszka
2015-02-12 17:01 ` Philippe Gerum
2015-02-12 17:02 ` Jan Kiszka [this message]
2015-02-12 17:07 ` Philippe Gerum
2015-02-12 17:16 ` Jan Kiszka
2015-02-12 17:18 ` Philippe Gerum
2015-02-12 17:19 ` Jan Kiszka
2015-02-12 17:45 ` Jan Kiszka
2015-02-16 17:37 ` Jan Kiszka
2015-02-16 17:43 ` Philippe Gerum
2015-02-17 10:58 ` 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=54DCDC98.5070402@siemens.com \
--to=jan.kiszka@siemens.com \
--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.