From: Luis Machado <luisgpm@br.ibm.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] "single step" atomic instruction sequences as a whole.
Date: Wed, 07 Feb 2007 13:10:00 -0000 [thread overview]
Message-ID: <200702071110.01767.luisgpm@br.ibm.com> (raw)
In-Reply-To: <20070206.211127.71089279.emi-suzuki@tjsys.co.jp>
Hi Emi,
It's great that we have someone working on this issue also.
What's exactly been modified on your patch for single stepping of atomic
instruction sequences? Does it handle the issues that you have mentioned
about thread hopping check?
Regards,
Luis
On Tuesday 06 February 2007 10:11, Emi SUZUKI wrote:
> Hello Luis and members,
>
> I am working on Linux running on PlayStation 3, and on Fedora Core 5
> for PowerPC running on our own hardware equipped with 'Cell' CPU.
> I have also been annoyed by this problem for months, because the main
> core of Cell is PowerPC.
>
> As far as I know, the patch by Paul has a problem mentioned by the
> messages below:
> http://sourceware.org/ml/gdb-patches/2006-09/msg00060.html
> http://sourceware.org/ml/gdb-patches/2006-09/msg00097.html
> http://sourceware.org/ml/gdb-patches/2006-11/msg00049.html
> http://sourceware.org/ml/gdb-patches/2006-11/msg00074.html
>
> And the idea is a bit confusing for me...
>
> I just thought that SOFTWARE_SINGLE_STEP_P should indicate if the
> target will do software single-stepping at the next time it proceed.
> And all the architectures which should skip atomic sequences of
> instructions by themselves need to implement are
> SOFTWARE_SINGLE_STEP_P to check if the skipping is needed, and
> SOFTWARE_SINGLE_STEP to actually skip the sequence.
> # I remember someone said that ARM and MIPS have a similar problem.
>
> As a effect of the change above, the return value of SOFTWARE_SINGLE_STEP_P
> cannot be used as the condition of thread hopping check or removing
> a software single-stepping breakpoint on handle_inferior_event: it
> may not be welcomed.
>
> Anyway, I will attach a patch applied on our environment. It's for
> CVS head.
> Since it's my first time of posting here, any comments are very
> appreciated.
>
> P.S.
> I have not completed the legal process of copyright assignment, and
> unfortunately the boss said to me that it will take months...
> Please point me if the patch can be applied and surely needs an
> assignment, I will make them hurry.
next prev parent reply other threads:[~2007-02-07 13:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 11:02 Luis Machado
2007-02-06 12:11 ` Emi SUZUKI
2007-02-07 13:10 ` Luis Machado [this message]
2007-02-08 13:00 ` Emi SUZUKI
-- strict thread matches above, loose matches on Subject: below --
2007-03-15 22:24 Luis Machado
2007-04-10 20:40 ` Daniel Jacobowitz
2007-04-12 12:09 ` Luis Machado
2007-04-12 12:15 ` Daniel Jacobowitz
2007-04-12 12:54 ` Luis Machado
2007-04-12 12:58 ` Daniel Jacobowitz
2007-04-12 13:30 ` Luis Machado
2007-04-12 13:35 ` Daniel Jacobowitz
2007-04-12 14:58 ` Ulrich Weigand
2007-04-12 15:33 ` Daniel Jacobowitz
2007-04-12 17:16 ` Ulrich Weigand
2007-04-12 18:25 ` Daniel Jacobowitz
2007-04-12 20:09 ` Ulrich Weigand
2007-04-12 20:16 ` Mark Kettenis
2007-04-12 20:43 ` Ulrich Weigand
2007-04-14 15:20 ` Mark Kettenis
2007-04-14 18:13 ` Ulrich Weigand
2007-04-12 20:49 ` Daniel Jacobowitz
2007-04-12 20:48 ` Daniel Jacobowitz
2007-04-12 14:32 ` Ulrich Weigand
2007-04-12 14:47 ` Luis Machado
2007-04-12 15:00 ` Ulrich Weigand
2007-02-17 2:24 Luis Machado
2007-02-27 13:00 ` Emi SUZUKI
2007-02-27 13:17 ` Daniel Jacobowitz
2007-02-28 8:08 ` Emi SUZUKI
2007-02-28 11:46 ` Daniel Jacobowitz
2007-02-28 16:09 ` Luis Machado
2007-03-02 12:47 ` Emi SUZUKI
2007-03-06 11:00 ` Andreas Schwab
2007-03-06 12:24 ` Daniel Jacobowitz
2007-03-08 8:50 ` Emi SUZUKI
2007-03-08 16:15 ` Ulrich Weigand
2007-03-13 6:12 ` SUZUKI Emi
2006-09-18 11:59 emin ak
2006-11-09 13:07 ` [patch] " emin ak
2006-06-22 20:56 PAUL GILLIAM
2006-06-22 21:53 ` PAUL GILLIAM
2006-06-22 22:20 ` PAUL GILLIAM
2006-11-10 21:18 ` Daniel Jacobowitz
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=200702071110.01767.luisgpm@br.ibm.com \
--to=luisgpm@br.ibm.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