Date: Mon, 7 Mar 2005 22:21:20 GMT From: John Baldwin <jhb@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 72667 for review Message-ID: <200503072221.j27MLKWu026883@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503072221.j27MLKWu026883>