From: Steven Seeger <steven.seeger@flightsystems.net>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@xenomai.org>, Philippe Gerum <rpm@xenomai.org>
Subject: Re: [PATCH] powerpc: ipipe: Do full exit checks after __ipipe_call_mayday
Date: Fri, 20 Dec 2019 18:38:52 -0500 [thread overview]
Message-ID: <6045179.LjjW8XADSc@omoikane> (raw)
In-Reply-To: <fd31a72f-ac46-034b-bfc6-4e125b4fde78@siemens.com>
On Thursday, December 19, 2019 11:53:36 AM EST Jan Kiszka wrote:
> > Ho, ho, this is an early X-mas gift.
Jan,
I got "gdb ok" when I removed the block I had in the entry_32.S I sent you
around the recheck/do_user_signal path. I was pretty sure I didn't need the
intret there.
Do you remember if you did that as well on your board?
This s the first time the test has passed for me without the extra trace
prints in smokey's gdb.c. In fact I got the latest xenomai next branch and
tested with that.
Some good news: your uclibc fix worked beautifully and I can now build the
stock xenomai distro with my board without any of my other patches.
I'm going to look at the mayday/DoSyscall issue you suggested now. I'll be
checking in a cleaned up entry_32.S as well. Will probably be Monday or so but
expect 20 more emails from me until then as per my usual pattern. (You cc'd
the list, so now the list must suffer the consequences of your actions.)
Steven
next prev parent reply other threads:[~2019-12-20 23:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 16:46 [PATCH] powerpc: ipipe: Do full exit checks after __ipipe_call_mayday Jan Kiszka
2019-12-19 16:53 ` Jan Kiszka
2019-12-19 17:01 ` Steven Seeger
2019-12-19 17:14 ` Jan Kiszka
2019-12-19 17:15 ` Steven Seeger
2019-12-19 17:24 ` Jan Kiszka
2019-12-21 0:14 ` Steven Seeger
2019-12-20 23:38 ` Steven Seeger [this message]
2019-12-21 12:09 ` Jan Kiszka
2019-12-20 22:19 ` Steven Seeger
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=6045179.LjjW8XADSc@omoikane \
--to=steven.seeger@flightsystems.net \
--cc=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.