From: Pedro Alves <pedro@codesourcery.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [MI] core awareness
Date: Mon, 11 Jan 2010 21:22:00 -0000 [thread overview]
Message-ID: <201001112122.08451.pedro@codesourcery.com> (raw)
In-Reply-To: <201001120001.08384.vladimir@codesourcery.com>
On Monday 11 January 2010 21:01:08, Vladimir Prus wrote:
> Implement core awareness.
>
> gdb/
> * bcache.c (compare_ints): Remove
> (print_percentage): Use compare_positive_ints.
>
> * defs.h (compare_positive_ints): Declare.
> * linux-nat.h (struct lin_lwp): New field core.
> (linux_nat_core_of_thread_1): Declare.
> * linux-nat.c (add_lwp): Init the 'core' field.
> (linux_nat_wait_1): Record the core.
> (linux_nat_core_of_thread_1, linux_nat_core_of_thread): New.
> (linux_nat_add_target): Register the above.
> * linux-thread-db.c (update_thread_core): New.
> (thread_db_find_new_threads): Update core information for
> every thread.
> * remote.c (struct private_thread_info): New.
> (free_private_thread_info, demand_private_info): New.
> (PACKET_qXfer_threads, use_osdata_threads): New.
> (struct thread_item, threads_parsing_context
> (start_thread, end_thread, thread_attributes)
> (thread_children, threads_children, threads_elements): New.
> (remote_threads_info): Try qXfer:threads before anything
> else.
> (remote_protocol_packets): Register qXfer:threads.
> (remote_open_1): Init use_osdata_threads.
> (struct stop_reply): New field 'core'.
> (remote_parse_stop_reply): Parse core number.
> (process_stop_reply): Record core number.
> (remote_xfer_partial): Handle qXfer:threads.
> (remote_core_of_thread): New.
> (init_remote_ops): Register remote_core_of_thread.
> (_initialize_remote): Register qXfer:read.
> * target.c (target_core_of_thread): New
> * target.h (enum target_object): New value TARGET_OBJECT_THREADS.
> (struct target_ops): New field to_core_of_threads.
> (target_core_of_thread): Declare.
> * gdbthread.h (struct thread_info): New field private_dtor.
> * thread.c (print_thread_info): Report the core.
> * ui-out.c (MAX_UI_OUT_LEVELS): Increase.
> * utils.c (compare_positive_ints): New.
> * features/threads.dtd: New.
> * mi/mi-interp.c (mi_on_normal_stop): Report the core.
> * mi/mi-main.c (struct collect_cores_data, collect_cores)
> (do_nothing, free_vector_of_osdata_items)
> (splay_tree_int_comparator, free_splay_tree): New.
> (print_one_inferior_data): Implemented printing of selected
> inferiors. Collect and print cores.
> (output_cores): New.
> (mi_cmd_list_thread_groups): Support --recurse. Permit specifying
> thread groups together with --available.
>
> gdbserver/
> * linux-low.c (linux_core_of_thread): New.
> (compare_ints, show_process, list_threads): New.
> (linux_qxfer_osdata): Report threads and cores.
> (linux_target_op): Register linux_core_of_thread.
> * remote-utils.c (prepare_resume_reply): Report the core.
> (buffer_xml_printf): Support %d specifier.
> * server.c (handle_threads_qxfer_proper, handle_threads_qxfer):
> New.
> (handle_query): Handle qXfer:threads. Announce availability
> thereof.
> * target.h (struct target_ops): New field core_of_thread.
This version is OK. Thanks.
--
Pedro Alves
next prev parent reply other threads:[~2010-01-11 21:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 15:33 Pedro Alves
2009-12-21 14:48 ` Vladimir Prus
2009-12-31 11:51 ` Pedro Alves
2010-01-04 15:11 ` Vladimir Prus
2010-01-08 20:30 ` Pedro Alves
2010-01-09 12:41 ` Vladimir Prus
2010-01-09 13:48 ` Eli Zaretskii
2010-01-11 14:17 ` Pedro Alves
2010-01-11 21:01 ` Vladimir Prus
2010-01-11 21:22 ` Pedro Alves [this message]
2010-01-12 21:44 ` Vladimir Prus
2010-01-12 22:56 ` Doug Evans
2010-01-12 23:08 ` Doug Evans
2010-01-13 5:21 ` Vladimir Prus
-- strict thread matches above, loose matches on Subject: below --
2009-12-16 20:53 Vladimir Prus
2009-12-17 15:31 ` Pedro Alves
2009-12-18 11:41 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201001112122.08451.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox