Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedro@codesourcery.com (Pedro Alves)
Cc: tromey@redhat.com (Tom Tromey),
	markus@hyperion-imrt.org (Markus Alber),
	       msnyder@vmware.com (Michael Snyder),
	gdb@sourceware.org
Subject: Re: performance of multithreading gets gradually worse under gdb
Date: Fri, 04 Feb 2011 15:13:00 -0000	[thread overview]
Message-ID: <201102041513.p14FDV8I030471@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <201102041455.20607.pedro@codesourcery.com> from "Pedro Alves" at Feb 04, 2011 02:55:20 PM

Pedro Alves wrote:

> > (Actually, now that every thread always has a thread_info, the
> > best thing would probably be anyway to hang each thread's regcaches
> > off the thread_info, and do away with the global list completely.)
> 
> Not sure we can do that yet, at least as sole mechanism to
> keep track of regcache pointers.
> We have targets that do thread<->lwp ptid translation between
> thread/proc stratum layers, and random places that do
> get_thread_regcache (ptid) behind the core's back -- it appears
> aix-thread.c could be one of those.
> Another example: linux-nat.c:cancel_breakpoint builds
> regcaches for lwps before linux-thread-db.c (if active at all)
> has had a chance of telling the core about new
> threads (in all-stop mode).

Ah, I see.  Yes, this looks like some more work is needed ...

Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2011-02-04 15:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 20:16 Markus Alber
2011-02-02 20:28 ` Michael Snyder
     [not found]   ` <76bccf1875854ebc69b6a892fb84a976@hyperion-imrt.org>
2011-02-02 21:43     ` Michael Snyder
2011-02-03  7:03       ` Markus Alber
2011-02-03 20:26         ` Michael Snyder
2011-02-03 20:52           ` Markus Alber
2011-02-03 20:57         ` Tom Tromey
2011-02-03 21:00           ` Tom Tromey
2011-02-03 21:40           ` Ulrich Weigand
2011-02-03 22:04             ` Tom Tromey
2011-02-04 13:49               ` Ulrich Weigand
2011-02-04 14:55             ` Pedro Alves
2011-02-04 15:13               ` Ulrich Weigand [this message]
2011-02-04 15:26               ` Tom Tromey
2011-02-04 15:56                 ` Pedro Alves
     [not found]                 ` <201102041555.52179.pedro__21913.9744448059$1296834976$gmane$org@codesourcery.com>
2011-02-04 17:02                   ` Tom Tromey
2011-02-05  9:34                     ` Markus Alber
2011-02-07 14:05                     ` Markus Alber

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=201102041513.p14FDV8I030471@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gdb@sourceware.org \
    --cc=markus@hyperion-imrt.org \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.com \
    --cc=tromey@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