From: Jan Kiszka <jan.kiszka@domain.hid>
To: rpm@xenomai.org
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH] Suppress switch warnings while debugging
Date: Tue, 10 Mar 2009 11:02:27 +0100 [thread overview]
Message-ID: <49B63AB3.7000801@domain.hid> (raw)
In-Reply-To: <49B63965.8090604@domain.hid>
Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>> Jan Kiszka wrote:
>>>> Don't raise SIGXCPU while the process is being debugged. These mode
>>>> changes are expected, and reporting them doesn't provide any helpful
>>>> information to the application. Rather, it may raise error storms on
>>>> the
>>>> application side.
>>>>
>>>> Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
>>>> ---
>>>>
>>>> ksrc/nucleus/shadow.c | 3 ++-
>>>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>>>
>>>> diff --git a/ksrc/nucleus/shadow.c b/ksrc/nucleus/shadow.c
>>>> index bcf3b8b..91cf499 100644
>>>> --- a/ksrc/nucleus/shadow.c
>>>> +++ b/ksrc/nucleus/shadow.c
>>>> @@ -1082,7 +1082,8 @@ void xnshadow_relax(int notify)
>>>>
>>>> xnstat_counter_inc(&thread->stat.ssw); /* Account for
>>>> secondary mode switch. */
>>>>
>>>> - if (notify && xnthread_test_state(thread, XNTRAPSW))
>>>> + if (notify && xnthread_test_state(thread, XNTRAPSW) &&
>>>> + !xnthread_test_state(thread, XNDEBUG))
>>>> /* Help debugging spurious relaxes. */
>>>> send_sig(SIGXCPU, current, 1);
>>>>
>>> I would rather identify the source of the switch and clear the notify
>>> flag appropriately from the relax call site.
>>
>> Sorry, don't get this: What flag do you want to clear? XNTRAPSW?
>>
>
> The "notify" parameter should set by the call site to tell
> xnshadow_relax() whether we want the SIGXCPU signal to be sent or not. I
> would rather identify which call site introduces the issue, and fix the
> notify parameter accordingly. Did you track the issue down to
> request_syscall_restart() for instance? In which case, we should rather
> test XNDEBUG there, and set the notify flag passed to xnshadow_relax()
> appropriately.
OK, now I understand. I didn't track this down yet, but it must be
request_syscall_restart, because that should be the only site that
relaxes due to pending signals. Will update the patch.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-03-10 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 9:06 [Xenomai-core] [PATCH] Suppress switch warnings while debugging Jan Kiszka
2009-03-10 9:30 ` Philippe Gerum
2009-03-10 9:41 ` Jan Kiszka
2009-03-10 9:56 ` Philippe Gerum
2009-03-10 10:02 ` Jan Kiszka [this message]
2009-03-10 10:32 ` [Xenomai-core] [PATCH v2] " 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=49B63AB3.7000801@domain.hid \
--to=jan.kiszka@domain.hid \
--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.