From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: fnf@specifix.com
Cc: gdb-patches@sources.redhat.com, fnf@specifix.com
Subject: Re: [RFC] Patch to add kernel threads support for FreeBSD 6.1
Date: Thu, 08 Feb 2007 21:47:00 -0000 [thread overview]
Message-ID: <200702082147.l18Ll7NU005756@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <200702061718.47875.fnf@specifix.com> (message from Fred Fish on Tue, 6 Feb 2007 17:18:47 -0700)
> From: Fred Fish <fnf@specifix.com>
> Date: Tue, 6 Feb 2007 17:18:47 -0700
>
> This patch adds support for kernel threads on FreeBSD 6.1. There are
> obviously some rough edges still, and I'd appreciate feedback from
> people with FreeBSD experience and also experience with thread support
> in gdb.
This looks quite reasonable. A couple of remarks:
Can you avoid introducing supply_xxregset()/fill_xxregset() and use
register sets instead?
Is the child_suppress_run hack really necessary? I thought the right
stratum was automatically chosen.
> +#define GET_PID(ptid) ptid_get_pid (ptid)
> +#define GET_LWP(ptid) ptid_get_lwp (ptid)
> +#define GET_THREAD(ptid) ptid_get_tid (ptid)
> +
> +#define IS_LWP(ptid) (GET_LWP (ptid) != 0)
> +#define IS_THREAD(ptid) (GET_THREAD (ptid) != 0)
> +
> +#define BUILD_LWP(lwp, pid) ptid_build (pid, lwp, 0)
> +#define BUILD_THREAD(tid, pid) ptid_build (pid, 0, tid)
These days these macros are really pointless and I think they should
die (here and elsewhere in the code).
Mark
next prev parent reply other threads:[~2007-02-08 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 0:19 Fred Fish
2007-02-08 21:47 ` Mark Kettenis [this message]
2007-02-08 23:05 ` Fred Fish
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=200702082147.l18Ll7NU005756@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=fnf@specifix.com \
--cc=gdb-patches@sources.redhat.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