Date: Thu, 27 Nov 2003 01:22:30 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: threads@freebsd.org Subject: Re: KSE/ia64 & thr_spinlock.c:1.18: problem identified Message-ID: <Pine.GSO.4.10.10311270114490.15725-100000@pcnet5.pcnet.com> In-Reply-To: <20031127055545.GB12712@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 kse_switchin()? BTW, why do we have to go through the kernel for ia64 in this case? -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10311270114490.15725-100000>