From: Luis Gustavo <luis_gustavo@mentor.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH, ppc] Fix hw *points for embedded ppc in a threaded environment.
Date: Tue, 07 Aug 2012 14:55:00 -0000 [thread overview]
Message-ID: <50212C53.3020109@mentor.com> (raw)
In-Reply-To: <20120806202734.GB2079@host2.jankratochvil.net>
On 08/06/2012 05:27 PM, Jan Kratochvil wrote:
> On Mon, 06 Aug 2012 21:02:11 +0200, Luis Gustavo wrote:
>> The ones you listed are server processors, and they use the old
>> kernel interface. Examples of BookE's are the 4xx family (405, 440,
>> 460, 476 etc...)
>
> OK, thanks for info. I do not think I have those available.
>
>
>> An appropriate test would be to run many threads and create the
>> maximum amount of hw watchpoints and see if that works fine, but
>> GDB's debug resource accounting is still a little awkward
>
> One can test the number of registers in singlethreaded testcase and then run
> the real test with multithreaded program.
Sounds good.
>
> A testcase would be nice, for example now the changes in
> archer-jankratochvil-watchpoint3 and pre-requisite of non-stop compatibility
> of hw watchpoints mean a lot of hw watchpoints rewrite in ppc-linux-nat.c.
>
> But if you are not going to write a testcase then I find it OK for both HEAD
> and 7.5.
I'm ok with coming up with that testcase. Should we go ahead and have
this in and the test commited shortly afterwards?
Luis
next prev parent reply other threads:[~2012-08-07 14:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 14:33 Luis Gustavo
2012-08-06 18:40 ` Jan Kratochvil
2012-08-06 19:02 ` Luis Gustavo
2012-08-06 20:28 ` Jan Kratochvil
2012-08-07 14:55 ` Luis Gustavo [this message]
2012-08-07 15:00 ` Jan Kratochvil
2012-08-07 15:02 ` Luis Gustavo
2012-12-27 19:50 ` Luis Machado
2013-01-22 12:12 ` Pedro Alves
2013-04-17 20:33 Luis Machado
2013-04-18 0:19 ` Sergio Durigan Junior
2013-04-18 0:51 ` Luis Machado
2013-04-22 21:09 ` Luis Machado
2013-04-22 21:09 ` Pedro Alves
2013-04-23 0:05 ` Pedro Alves
2013-04-23 1:15 ` Pedro Alves
2013-04-23 20:25 ` Luis Machado
2013-04-23 23:18 ` Luis Machado
2013-04-24 3:19 ` Pedro Alves
2013-04-24 6:28 ` Luis Machado
2013-04-24 19:04 ` Pedro Alves
2013-04-25 14:13 ` Luis Machado
2013-05-07 7:44 ` Luis Machado
2013-04-24 4:36 ` 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=50212C53.3020109@mentor.com \
--to=luis_gustavo@mentor.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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