From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sourceware.org
Subject: Re: [RFC] "single step" atomic instruction sequences as a whole on PPC
Date: Thu, 10 May 2007 00:48:00 -0000 [thread overview]
Message-ID: <1178758118.16015.12.camel@localhost> (raw)
In-Reply-To: <200705091945.l49Jjjf6030835@d12av02.megacenter.de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
> I'd just do "opcode = insn >> 26" same as in rs6000_software_single_step.
> (In fact I'm wondering why branch_dest doesn't just that for itself ...).
Follows the updated patch. The "opcode" variable is now being assigned
the correct instruction's opcode value (only the corresponding bits).
As a consequence of this change, i've noticed problems with branch
instructions next to the stwcx/stdcx instructions (the end of the
sequence). Getting the destination address of this type of branch could
potentially (upon a failing branch condition) lead to the function
placing a breakpoint right at the stwcx/stdcx instruction, thus leading
us back to the same locking problem.
The variable "closing_insn" was created to check if the breakpoint at
the branch instruction's destination is right at the stwcx/stdcx
instruction. If so, ignore this breakpoint and consider only the
breakpoint after the closing of the atomic sequence.
Regards,
Luis
[-- Attachment #2: fix_opcode_var.diff --]
[-- Type: text/x-patch, Size: 2322 bytes --]
2007-05-09 Luis Machado <luisgpm@br.ibm.com>
* rs6000-tdep.c: (deal_with_atomic_sequence) Stores branch instruction's
opcode in the "opcode" variable and declares new variable "closing_insn".
Index: gdb/rs6000-tdep.c
===================================================================
--- gdb.orig/rs6000-tdep.c 2007-05-09 12:19:29.000000000 -0700
+++ gdb/rs6000-tdep.c 2007-05-09 17:36:13.000000000 -0700
@@ -729,12 +729,13 @@
CORE_ADDR breaks[2] = {-1, -1};
CORE_ADDR loc = pc;
CORE_ADDR branch_bp; /* Breakpoint at branch instruction's destination. */
+ CORE_ADDR closing_insn; /* Instruction that closes the atomic sequence. */
int insn = read_memory_integer (loc, PPC_INSN_SIZE);
int insn_count;
int index;
int last_breakpoint = 0; /* Defaults to 0 (no breakpoints placed). */
const int atomic_sequence_length = 16; /* Instruction sequence length. */
- const int opcode = BC_INSTRUCTION; /* Branch instruction's OPcode. */
+ int opcode; /* Branch instruction's OPcode. */
int bc_insn_count = 0; /* Conditional branch instruction count. */
/* Assume all atomic sequences start with a lwarx/ldarx instruction. */
@@ -758,6 +759,7 @@
return 0; /* More than one conditional branch found, fallback
to the standard single-step code. */
+ opcode = insn >> 26;
branch_bp = branch_dest (opcode, insn, pc, breaks[0]);
if (branch_bp != -1)
@@ -778,14 +780,19 @@
&& (insn & STWCX_MASK) != STDCX_INSTRUCTION)
return 0;
+ closing_insn = loc;
loc += PPC_INSN_SIZE;
insn = read_memory_integer (loc, PPC_INSN_SIZE);
/* Insert a breakpoint right after the end of the atomic sequence. */
breaks[0] = loc;
- /* Check for duplicated breakpoints. */
- if (last_breakpoint && (breaks[1] == breaks[0]))
+ /* Check for duplicated breakpoints. Check also for a breakpoint
+ placed (branch instruction's destination) at the stwcx/stdcx
+ instruction, this resets the reservation and take us back to the
+ lwarx/ldarx instruction at the beginning of the atomic sequence. */
+ if (last_breakpoint && ((breaks[1] == breaks[0])
+ || (breaks[1] == closing_insn)))
last_breakpoint = 0;
/* Effectively inserts the breakpoints. */
next prev parent reply other threads:[~2007-05-10 0:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1177964763.15264.45.camel@localhost>
2007-05-02 14:08 ` uweigand
2007-05-03 14:51 ` Luis Machado
2007-05-06 21:20 ` Ulrich Weigand
2007-05-07 15:14 ` Luis Machado
2007-05-07 18:11 ` Ulrich Weigand
2007-05-07 19:28 ` Luis Machado
2007-05-07 22:47 ` Ulrich Weigand
2007-05-07 23:23 ` Luis Machado
2007-05-08 12:50 ` Ulrich Weigand
2007-05-09 14:33 ` Ulrich Weigand
2007-05-09 18:05 ` Luis Machado
2007-05-09 18:12 ` Daniel Jacobowitz
2007-05-09 18:21 ` Luis Machado
2007-05-09 18:34 ` Jan Kratochvil
2007-05-09 18:46 ` Daniel Jacobowitz
2007-05-09 19:10 ` Ulrich Weigand
2007-05-09 19:14 ` Luis Machado
2007-05-10 10:57 ` Emi SUZUKI
2007-05-10 21:31 ` Ulrich Weigand
2007-05-10 21:36 ` Daniel Jacobowitz
2007-05-10 22:58 ` Ulrich Weigand
2007-05-10 23:25 ` Daniel Jacobowitz
2007-05-11 7:34 ` Emi SUZUKI
2007-05-11 12:46 ` Ulrich Weigand
2007-05-09 19:45 ` Ulrich Weigand
2007-05-10 0:48 ` Luis Machado [this message]
2007-05-10 20:29 ` Ulrich Weigand
2007-04-09 2:13 Patch for gdb build on hppa hp-ux Daniel Jacobowitz
2007-04-09 23:25 ` Steve Ellcey
2007-04-10 12:05 ` Daniel Jacobowitz
2007-04-10 19:03 ` Eli Zaretskii
2007-04-10 20:22 ` Daniel Jacobowitz
2007-04-13 14:04 ` Daniel Jacobowitz
2007-04-13 17:07 ` [patch] "single step" atomic instruction sequences as a whole on PPC Luis Machado
2007-04-28 23:34 ` [RFC] " Luis Machado
2007-04-28 23:45 ` Ulrich Weigand
2007-04-29 1:53 ` Luis Machado
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=1178758118.16015.12.camel@localhost \
--to=luisgpm@linux.vnet.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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