summaryrefslogtreecommitdiffstats
path: root/sys/sparc64
diff options
context:
space:
mode:
authored <ed@FreeBSD.org>2008-08-24 15:20:44 +0000
committered <ed@FreeBSD.org>2008-08-24 15:20:44 +0000
commitfc03269bd377fdba1743efebf7c4c4326a09c659 (patch)
treee275d30a75e5c9ee45dc8593e8b169fcfd044361 /sys/sparc64
parent5e0a924fecb528e064546f1f0aff20da81027b70 (diff)
downloadFreeBSD-src-fc03269bd377fdba1743efebf7c4c4326a09c659.zip
FreeBSD-src-fc03269bd377fdba1743efebf7c4c4326a09c659.tar.gz
Make sysmouse(4) use its own locks, instead of using Giant.
When I changed syscons(4) to work with the MPSAFE TTY code, I just locked all device nodes down using the compatibility feature that allows you to override the TTY's lock (Giant in this case). Upon closer inspection, it seems sysmouse(4) only has two internal variables that need locking: mouse_level and mouse_status. I haven't done any performance benchmarks on this, though I think it won't have any dramatic improvements on the system. It is good to get rid of Giant here, because the third argument of tty_alloc() has only been added to ease migration to MPSAFE TTY. It should not be used when not needed. While there, remove SC_MOUSE, which is a leftover from the MPSAFE TTY import.
Diffstat (limited to 'sys/sparc64')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud