From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: [PATCH] kgdb/x86 over I-pipe
Date: Thu, 15 Jun 2006 14:42:43 +0200 [thread overview]
Message-ID: <449155C3.6030502@domain.hid> (raw)
In-Reply-To: <448D337F.9060002@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Philippe Gerum wrote:
>>> While we are at it,
>>> #define current ipipe_safe_current() /* ? */
>>
>>
>> Nope, there is the need for some special changes.
>>
>
> If you refer to the cache flushing issue, then it would be better to
> actually check for foreign stacks explicitely, so that you could
> substitute current globally:
>
> - if (CACHE_FLUSH_IS_SAFE && current->mm &&
> - addr < TASK_SIZE)
> + if (CACHE_FLUSH_IS_SAFE && !testbit(IPIPE_NOSTACK_FLAG,
> + &ipipe_percpu_domain[cpuid]->cpudata[cpuid].status) &&
> + current->mm && addr < TASK_SIZE)
>
Right - on first sight. I tried to redefine current, but the
ipipe_safe_current macro requires that symbol itself, ugh. Turning
ipipe_safe_current into a static inline doesn't work due to circular
dependencies on linux/sched.h.
So I guess it's best to keep it as it is (though kgdb-ipipe.patch would
have become really cute).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-06-15 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 19:06 [Xenomai-core] [PATCH] kgdb-ipipe for 2.6.16 Jan Kiszka
2006-06-01 8:00 ` Jan Kiszka
2006-06-07 16:19 ` [Xenomai-core] [PATCH] kgdb/x86 over I-pipe Philippe Gerum
2006-06-07 16:50 ` [Xenomai-core] " Jan Kiszka
2006-06-08 8:24 ` Philippe Gerum
2006-06-10 22:19 ` Jan Kiszka
2006-06-12 8:27 ` Philippe Gerum
2006-06-12 8:40 ` Jan Kiszka
2006-06-12 9:27 ` Philippe Gerum
2006-06-15 12:42 ` Jan Kiszka [this message]
2006-06-15 14:24 ` 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=449155C3.6030502@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.