Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [RFC: 0/9] No context-switching
Date: Sat, 16 Aug 2008 15:29:00 -0000	[thread overview]
Message-ID: <200808161629.12044.pedro@codesourcery.com> (raw)

This series of patches removes inferior control globals, in favour of 
accessing thread_info members directly, effectivelly, getting rid of
the need to context-switch.

I've layed out the series so it is always functional at all of
its incremental steps.  At the end of the series, context_switch will
just be a wrapper around switch_to_thread.  I still left that function
around, mainly, for "set debug infrun 1" purposes (it prints an
useful message).

I've tested the whole series on x86_64-unknown-linux-gnu,
i386-unknown-openbsd4.3, i386-pc-solaris2.11, i686-pc-cygwin,
and arm-none-linux-gnu (to cover software single-step), I found no
regressions.

This series depends on having all targets register the main thread
in the the thread list, even when debugging a single-threaded
inferior.  Patches for most of the targets have been posted
already, most approved.

I believe the only missing targets to adjust are AIX,
remote-mips.c, nto-procfs.c.  I've talked with Aleksandar about
nto, and we came to the conclusion that nto is easy to fix.
remote-mips.c should be as similarly easy to remote-m32-sdi.c,
monitor.c or remote-sim.c.  I'll try to give another look at
AIX this weekend, and browse over IBM's documentation, to see if
I can come up with an initial patch, but it doesn't seem likelly,
with no AIX access.

In the mean time, I thought I'd post this series as an RFC.

-- 
Pedro Alves


             reply	other threads:[~2008-08-16 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-16 15:29 Pedro Alves [this message]
2008-08-18 12:10 ` Joel Brobecker
2008-09-02 23:44 ` Daniel Jacobowitz
2008-09-08 22:15   ` Pedro Alves

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=200808161629.12044.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.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