[PATCH 0/4] Reduce back and forth with target when threads have

[Simon Marchi]

The goal of this series is to make it able for infrun to tell the target
when it needs it to commit resumed threads to the execution device, and
when it's ok to defer doing that.  When infrun knows it will do more
operations (for example, it is resuming/stopping many threads, or it
knows it has pending events to process), it uses that to let the target
defer moving resumed threads to the execution device until all these
operations are done.  This is explained in details in the last patch.

I'm not 100% happy with the new naming, so if you have comments about
that, I'll gladly take them.

Note that I tested this series on top of these other series:

    https://sourceware.org/pipermail/gdb-patches/2020-December/174165.html
    https://sourceware.org/pipermail/gdb-patches/2020-December/174117.html
    https://sourceware.org/pipermail/gdb-patches/2020-November/173633.html

In theory, they are not dependent, I'm mentioning it just in case, we
never know.

Simon Marchi (4):
  gdb: make remote target track resumed but no vCont-resumed threads
  gdb: remove target_ops::commit_resume implementation in
    record-{btrace,full}.c
  gdb: move commit_resume to process_stratum_target
  gdb: generalize commit_resume, avoid commit-resuming when threads have
    pending statuses

 gdb/infcmd.c                 |   8 ++
 gdb/infrun.c                 | 126 ++++++++++++++---
 gdb/infrun.h                 |  41 ++++++
 gdb/linux-nat.c              |   5 +
 gdb/mi/mi-main.c             |   2 +
 gdb/process-stratum-target.c |  14 ++
 gdb/process-stratum-target.h |  38 +++++
 gdb/record-btrace.c          |  11 --
 gdb/record-full.c            |  20 +--
 gdb/remote.c                 | 262 ++++++++++++++++++++++++++---------
 gdb/target-delegates.c       |  22 ---
 gdb/target.c                 |  22 ---
 gdb/target.h                 |  20 ---
 13 files changed, 412 insertions(+), 179 deletions(-)

-- 
2.29.2