KSE/ia64 & thr_spinlock.c:1.18: problem identified

Daniel Eischen eischen at vigrid.com
Wed Nov 26 22:22:32 PST 2003

On Wed, 26 Nov 2003, Marcel Moolenaar wrote:

> Ok,
> I found what the problem is. Syscalls that got interrupted were not
> restarted when they should be. This is the result of using the KSE
> internal context functions, when we should be going through the
> kernel. So, the end result is that we do in fact need a syscall to
> switch KSE contexts. Attached a patch to add such syscall. Please
> review (ia64 specific changes to make use of the syscall are not
> included).

We don't need this for x86 or amd64, at least AFAICT, correct?
How does a context get marked so one knows that you need to use

BTW, why do we have to go through the kernel for ia64 in this

Dan Eischen

More information about the freebsd-threads mailing list