From owner-freebsd-arch Fri Feb 15 23:38: 6 2002 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (dhcp28.gw.tislabs.com [192.94.214.128]) by hub.freebsd.org (Postfix) with ESMTP id 4FD9B37B402; Fri, 15 Feb 2002 23:38:01 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g1G7XHW06990; Sat, 16 Feb 2002 08:33:31 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: arch@freebsd.org, jhb@freebsd.org, peter@wemm.org, jake@locore.ca Subject: Re: gettimeofday() and copyout(). Is copyout() MPSAFE on non-i386 archs? In-Reply-To: Your message of "Fri, 15 Feb 2002 21:00:45 PST." <200202160500.g1G50j145638@apollo.backplane.com> Date: Sat, 16 Feb 2002 08:33:17 +0100 Message-ID: <6988.1013844797@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202160500.g1G50j145638@apollo.backplane.com>, Matthew Dillon wri tes: > Poul indicated today that the microtime() call that gettimeofday() uses > is MPSAFE. copyout() on I386 is MPSAFE, and from my perusal of the > other archs it appears to be MPSAFE for alpha, ia64, and sparc64 > as well. > > This would seem to indicate that Giant can be removed from the > gettimeofday() system call. I would like those familiar with the > other archs to verify that copyout() is MPSAFE on them. I am testing > Giant removal for this syscall on i386 now. Make sure to run something which abuses gettimeofday() for select, maybe netscape or some other multi-threaded nightmare. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message