summaryrefslogtreecommitdiff
path: root/gdbsupport
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@polymtl.ca>2021-06-21 14:26:36 -0400
committerSimon Marchi <simon.marchi@polymtl.ca>2021-07-12 20:46:53 -0400
commita66f72981979a1bda60805b8554e0c78c4a39a21 (patch)
treef48ef0253d06cf850a822c8fbc7b1d9285f4071d /gdbsupport
parent1edb66d856c82c389edfd7610143236a68c76846 (diff)
gdb: maintain per-process-target list of resumed threads with pending wait status
Looking up threads that are both resumed and have a pending wait status to report is something that we do quite often in the fast path and is expensive if there are many threads, since it currently requires walking whole thread lists. The first instance is in maybe_set_commit_resumed_all_targets. This is called after handling each event in fetch_inferior_event, to see if we should ask targets to commit their resumed threads or not. If at least one thread is resumed but has a pending wait status, we don't ask the targets to commit their resumed threads, because we want to consume and handle the pending wait status first. The second instance is in random_pending_event_thread, where we want to select a random thread among all those that are resumed and have a pending wait status. This is called every time we try to consume events, to see if there are any pending events that we we want to consume, before asking the targets for more events. To allow optimizing these cases, maintain a per-process-target list of threads that are resumed and have a pending wait status. In maybe_set_commit_resumed_all_targets, we'll be able to check in O(1) if there are any such threads simply by checking whether the list is empty. In random_pending_event_thread, we'll be able to use that list, which will be quicker than iterating the list of threads, especially when there are no resumed with pending wait status threads. About implementation details: using the new setters on class thread_info, it's relatively easy to maintain that list. Any time the "resumed" or "pending wait status" property is changed, we check whether that should cause the thread to be added or removed from the list. In set_thread_exited, we try to remove the thread from the list, because keeping an exited thread in that list would make no sense (especially if the thread is freed). My first implementation assumed that a process stratum target was always present when set_thread_exited is called. That's however, not the case: in some cases, targets unpush themselves from an inferior and then call "exit_inferior", which exits all the threads. If the target is unpushed before set_thread_exited is called on the threads, it means we could mistakenly leave some threads in the list. I tried to see how hard it would be to make it such that targets have to exit all threads before unpushing themselves from the inferior (that would seem logical to me, we don't want threads belonging to an inferior that has no process target). That seemed quite difficult and not worth the time at the moment. Instead, I changed inferior::unpush_target to remove all threads of that inferior from the list. As of this patch, the list is not used, this is done in the subsequent patches. The debug messages in process-stratum-target.c need to print some ptids. However, they can't use target_pid_to_str to print them without introducing a dependency on the current inferior (the current inferior is used to get the current target stack). For debug messages, I find it clearer to print the spelled out ptid anyway (the pid, lwp and tid values). Add a ptid_t::to_string method that returns a string representation of the ptid that is meant for debug messages, a bit like we already have frame_id::to_string. Change-Id: Iad8f93db2d13984dd5aa5867db940ed1169dbb67
Diffstat (limited to 'gdbsupport')
-rw-r--r--gdbsupport/ptid.cc8
-rw-r--r--gdbsupport/ptid.h7
2 files changed, 15 insertions, 0 deletions
diff --git a/gdbsupport/ptid.cc b/gdbsupport/ptid.cc
index 73e2918cbc..2417120b1e 100644
--- a/gdbsupport/ptid.cc
+++ b/gdbsupport/ptid.cc
@@ -24,3 +24,11 @@
ptid_t const null_ptid = ptid_t::make_null ();
ptid_t const minus_one_ptid = ptid_t::make_minus_one ();
+
+/* See ptid.h. */
+
+std::string
+ptid_t::to_string () const
+{
+ return string_printf ("%d.%ld.%ld", m_pid, m_lwp, m_tid);
+}
diff --git a/gdbsupport/ptid.h b/gdbsupport/ptid.h
index a0a91758b3..a2553b29c1 100644
--- a/gdbsupport/ptid.h
+++ b/gdbsupport/ptid.h
@@ -33,6 +33,7 @@
*/
#include <functional>
+#include <string>
class ptid_t
{
@@ -124,6 +125,12 @@ public:
|| *this == filter);
}
+ /* Return a string representation of the ptid.
+
+ This is only meant to be used in debug messages. */
+
+ std::string to_string () const;
+
/* Make a null ptid. */
static constexpr ptid_t make_null ()