From owner-freebsd-current Sun Jan 31 01:46:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04801 for freebsd-current-outgoing; Sun, 31 Jan 1999 01:46:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04794 for ; Sun, 31 Jan 1999 01:46:53 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id EAA21245; Sun, 31 Jan 1999 04:40:59 -0500 (EST) From: Peter Dufault Message-Id: <199901310940.EAA21245@hda.hda.com> Subject: Re: LINUX clone? sched_yield? In-Reply-To: <199901310414.PAA15601@godzilla.zeta.org.au> from Bruce Evans at "Jan 31, 99 03:14:18 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 31 Jan 1999 04:40:58 -0500 (EST) Cc: dufault@hda.com, wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There's a yield() syscall that is enabled permanently. Is there any > harm in untangling it from the POSIX sched_yield()? :-) I've got a synch_yield() in kern_synch and a call into it from yield() in kern_thread that duplicates the yield() behavior for the non-RTPRIO, non-sched_yield() condition. synch_yield() also KASSERTS that p == curproc since nothing else makes sense. However, I've woken up to a gcc SIG 11 during my world build. This is from yesterday AM sources and is the first crash for my crash box. Though I doubt it is my patches I'll look a bit to convince myself. Prior to this that system has been running a week with a patched world. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message