Skip to content
Snippets Groups Projects
Select Git revision
  • dailybuild_linux-x64
  • dailybuild_win32
  • master default protected
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • new_user_dat
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
40 results

vidmodes.c

Blame
    • deuce's avatar
      4d70127d
      Improve the locking "stuff"... · 4d70127d
      deuce authored
      For regular vstatlock things, only hold the lock long enough to copy the
      variables that will be used.
      
      For vstat.vmem stuff, create a separate reference-counting vmem structure
      and a new vmem_lock so the memcpy() of the vmem won't block basic vstat
      accesses.
      
      This appears to fix the recently-added "blockiness" of screen updates in
      SyncTERM, without risking deadlocks or unlocked accesses... the major issue
      holding up a release.
      4d70127d
      History
      Improve the locking "stuff"...
      deuce authored
      For regular vstatlock things, only hold the lock long enough to copy the
      variables that will be used.
      
      For vstat.vmem stuff, create a separate reference-counting vmem structure
      and a new vmem_lock so the memcpy() of the vmem won't block basic vstat
      accesses.
      
      This appears to fix the recently-added "blockiness" of screen updates in
      SyncTERM, without risking deadlocks or unlocked accesses... the major issue
      holding up a release.