[v4,0/6] Refinement of scheduler-locking settings

Message ID 20251213143709.301799-1-christina.schimpe@intel.com
Headers
Series Refinement of scheduler-locking settings |

Message

Schimpe, Christina Dec. 13, 2025, 2:37 p.m. UTC
  I rebased this on Klaus' behalf to make the review easier, since there
are conflicts with current master for v3, as Guinevere points out
(thanks again!).

https://sourceware.org/pipermail/gdb-patches/2025-December/223164.html

So besides the resolved conflicts (mainly with patch #1), this series
did not change.

Changes since v3:
Adapt patch #1, to adapt for upstream master changes:
schedlock_applies (bool step) -> schedlock_applies (bool step, bool record_will_replay)

Thanks,
Christina


Natalia Saiapova (6):
  gdb: use schedlock_applies in user_visible_resume_ptid.
  gdb, cli: remove left-over code from "set_logging_on".
  gdb, cli: pass the argument of a set command to its callback.
  gdb: change the internal representation of scheduler locking.
  gdb: refine commands to control scheduler locking.
  gdb: add eval option to lock the scheduler during infcalls.

 gdb/NEWS                                      |  25 ++
 gdb/cli/cli-logging.c                         |   5 -
 gdb/cli/cli-setshow.c                         |   2 +-
 gdb/doc/gdb.texinfo                           |  82 +++-
 gdb/infrun.c                                  | 415 +++++++++++++++---
 .../gdb.mi/user-selected-context-sync.exp     |  23 +-
 .../gdb.threads/hand-call-in-threads.exp      |  12 +-
 .../multiple-successive-infcall.exp           |   7 +-
 gdb/testsuite/gdb.threads/schedlock.exp       | 105 ++++-
 gdb/testsuite/lib/gdb.exp                     |  71 ++-
 10 files changed, 626 insertions(+), 121 deletions(-)