From owner-p4-projects@FreeBSD.ORG Mon Mar 7 22:21:21 2005 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 01FA616A4D6; Mon, 7 Mar 2005 22:21:21 +0000 (GMT) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7DE116A4D0 for ; Mon, 7 Mar 2005 22:21:20 +0000 (GMT) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F56443D67 for ; Mon, 7 Mar 2005 22:21:20 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.13.1/8.13.1) with ESMTP id j27MLK3r026886 for ; Mon, 7 Mar 2005 22:21:20 GMT (envelope-from jhb@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.13.1/8.13.1/Submit) id j27MLKWu026883 for perforce@freebsd.org; Mon, 7 Mar 2005 22:21:20 GMT (envelope-from jhb@freebsd.org) Date: Mon, 7 Mar 2005 22:21:20 GMT Message-Id: <200503072221.j27MLKWu026883@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to jhb@freebsd.org using -f From: John Baldwin To: Perforce Change Reviews Subject: PERFORCE change 72667 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2005 22:21:21 -0000 http://perforce.freebsd.org/chv.cgi?CH=72667 Change 72667 by jhb@jhb_slimer on 2005/03/07 22:21:08 Update. Affected files ... .. //depot/projects/smpng/sys/notes#30 edit Differences ... ==== //depot/projects/smpng/sys/notes#30 (text+ko) ==== @@ -19,6 +19,33 @@ more realistic since they call functions. However, these clobber updates need to be verified against the actual pc98 code. - Untested + - Oops, '+' is invalid for memory operands it turns out, so revisit the + whole tree to really fix this. Also, fixup atomic ops so that they + treat the memory pointed to as an output and don't all clobber "memory", + instead, just acquire variants clobber "memory". + + alpha + + amd64 + - why clobber memory in disable_intr()? + - eventually we should not clobber all memory for bus_space, but just + the memory we actually touch + + arm + - needs real acq variants to get "memory" clobber + + boot + + contrib + + dev + - drm clobbers memory for write barriers + - drm and sym should use bus_space for barriers + - gnu + - contrib code + + ia64 + + i386 + - why clobber memory in disable_intr()? + + pc98 + + pci + + powerpc + - not sure powerpc_mb() should clobber memory + + sparc64 + - sys - Fixup td_ucred of thread doing execve() to re-sync with process ucred after single threading during an exec. - Untested