PERFORCE change 84076 for review
John Baldwin
jhb at FreeBSD.org
Wed Sep 21 14:02:28 PDT 2005
http://perforce.freebsd.org/chv.cgi?CH=84076
Change 84076 by jhb at jhb_slimer on 2005/09/21 21:01:48
Update.
Affected files ...
.. //depot/projects/smpng/sys/notes#57 edit
Differences ...
==== //depot/projects/smpng/sys/notes#57 (text+ko) ====
@@ -9,36 +9,31 @@
for inline asm stuff. For pc98 I tried to update the clobbers to be
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".
- - Put off the relaxing of memory clobbers to just acquire variants until
- later
- - 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, then __swp() can stop
- clobbering "memory"
- - 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
- - powerpc
- - not sure powerpc_mb() should clobber memory
- - sparc64
- - sys
- + start over saving current state in the ktrace branch so I can break this up
- - see what's left of the diff after these
+ - Moved to the jhb_ktrace branch for now. Also, haven't removed the
+ "cc" clobbers yet.
+- 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, then __swp() can stop
+ clobbering "memory"
+ - 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
+ - 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
More information about the p4-projects
mailing list