From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@FreeBSD.org>,
gdb-patches@sourceware.org, binutils@sourceware.org,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v3 5/6] Add support for LWP-based threads on FreeBSD.
Date: Mon, 18 Jan 2016 12:37:00 -0000 [thread overview]
Message-ID: <569CDC86.6090003@redhat.com> (raw)
In-Reply-To: <1453084047-16175-6-git-send-email-jhb@FreeBSD.org>
Eli, this revision includes NEWS/docs bits.
On 01/18/2016 02:27 AM, John Baldwin wrote:
> Older versions of FreeBSD supported userland threading via a pure
> user-space threading library (N threads scheduled on 1 process) and
> a N:M model (N threads scheduled on M LWPs). However, modern FreeBSD
> versions only support a M:M threading model where each user thread is
> backed by a dedicated LWP. This thread target only supports this
> threading model. It also uses ptrace to query and alter LWP state
> directly rather than using libthread_db to simplify the implementation.
>
> FreeBSD recently gained support for reporting LWP events (birth and death
> of LWPs). GDB will use LWP events when present. For older systems it
> fetches the list of LWPs in the to_update_thread_list target op to update
> the list of threads on each stop.
>
> This target supports scheduler locking by using ptrace to suspend
> individual LWPs as necessary before resuming a process.
Code changes LGTM.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-01-18 12:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 2:28 [PATCH v3 0/6] Support kernel-backed user " John Baldwin
2016-01-18 2:28 ` [PATCH v3 1/6] Add support to readelf for reading FreeBSD ELF core notes John Baldwin
2016-01-19 16:50 ` Christophe Lyon
2016-01-19 17:10 ` John Baldwin
2016-01-19 17:12 ` Pedro Alves
2016-01-18 2:28 ` [PATCH v3 3/6] Display per-thread information for threads in FreeBSD cores John Baldwin
2016-01-18 2:28 ` [PATCH v3 6/6] Dump register notes for each thread when generating a FreeBSD core John Baldwin
2016-01-18 12:38 ` Pedro Alves
2016-01-18 2:28 ` [PATCH v3 2/6] Add a psuedosection for the NT_FREEBSD_THRMISC note John Baldwin
2016-01-18 12:38 ` Pedro Alves
2016-01-18 17:06 ` John Baldwin
2016-01-18 2:28 ` [PATCH v3 4/6] Use LWP IDs with ptrace register requests on FreeBSD John Baldwin
2016-01-18 12:32 ` Pedro Alves
2016-01-18 2:28 ` [PATCH v3 5/6] Add support for LWP-based threads " John Baldwin
2016-01-18 12:37 ` Pedro Alves [this message]
2016-01-18 16:00 ` Eli Zaretskii
2016-01-18 17:06 ` John Baldwin
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=569CDC86.6090003@redhat.com \
--to=palves@redhat.com \
--cc=binutils@sourceware.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).