All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: "Amit S. Kale" <amitkale@emsyssoft.com>
Cc: Powerpc Linux <linuxppc-dev@lists.linuxppc.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>,
	George Anzinger <george@mvista.com>
Subject: Re: PPC KGDB changes and some help?
Date: Thu, 22 Jan 2004 11:05:55 -0700	[thread overview]
Message-ID: <20040122180555.GK15271@stop.crashing.org> (raw)
In-Reply-To: <20040122174416.GJ15271@stop.crashing.org>

On Thu, Jan 22, 2004 at 10:44:16AM -0700, Tom Rini wrote:
> On Wed, Jan 21, 2004 at 12:22:30PM -0700, Tom Rini wrote:
> > On Wed, Jan 21, 2004 at 12:21:28PM -0700, Tom Rini wrote:
> > > On Wed, Jan 21, 2004 at 11:42:17AM -0700, Tom Rini wrote:
> > > > On Wed, Jan 21, 2004 at 10:23:12PM +0530, Amit S. Kale wrote:
> > > > 
> > > > > Hi,
> > > > > 
> > > > > Here it is: ppc kgdb from timesys kernel is available at
> > > > > http://kgdb.sourceforge.net/kgdb-2/linux-2.6.1-kgdb-2.1.0.tar.bz2
> > > > > 
> > > > > This is my attempt at extracting kgdb from TimeSys kernel. It works well in 
> > > > > TimeSys kernel, so blame me if above patch doesn't work.
> > > > 
> > > > Okay, here's my first patch against this.
> > > 
> > > And dependant upon this is a patch to fixup the rest of the common PPC
> > > code, as follows:
> > 
> > And on top of all of that is the following, which allows KGDB to work on
> > the Motorola LoPEC.
> 
> On top of everything from yesterday, here's:

First up:
We need to call flush_instruction_cache() on a 'c' or 's' command.
 arch/ppc/kernel/ppc-stub.c |   19 ++++++-------------
 1 files changed, 6 insertions(+), 13 deletions(-)
--- 1.14/arch/ppc/kernel/ppc-stub.c	Thu Jan 22 10:41:58 2004
+++ edited/arch/ppc/kernel/ppc-stub.c	Thu Jan 22 10:49:30 2004
@@ -144,18 +144,6 @@
 	return;
 }				/* gdb_regs_to_regs */
 
-/* exit_handler:
- * 
- * This is called by the generic layer when it is about to return from 
- * the exception handler
- */
-void
-ppc_handler_exit(void)
-{
-//      flush_instruction_cache ();
-	return;
-}
-
 /*
  * This function does PoerPC specific procesing for interfacing to gdb.
  */
@@ -188,6 +176,12 @@
 		if (kgdb_hexToLong(&ptr, &addr))
 			linux_regs->nip = addr;
 
+/* Need to flush the instruction cache here, as we may have deposited a
+ * breakpoint, and the icache probably has no way of knowing that a data ref to
+ * some location may have changed something that is in the instruction cache.
+ */
+		flush_instruction_cache();
+
 		/* set the trace bit if we're stepping */
 		if (remcomInBuffer[0] == 's') {
 #if defined (CONFIG_4xx)
@@ -254,5 +248,4 @@
 	.sleeping_thread_to_gdb_regs = ppc_sleeping_thread_to_gdb_regs,
 	.gdb_regs_to_regs = ppc_gdb_regs_to_regs,
 	.handle_exception = ppc_handle_exception,
-	.handler_exit = ppc_handler_exit,
 };

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2004-01-22 18:06 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040120172708.GN13454@stop.crashing.org>
2004-01-21 14:16 ` PPC KGDB changes and some help? Amit S. Kale
2004-01-21 15:30   ` Tom Rini
2004-01-21 16:53     ` Amit S. Kale
2004-01-21 18:42       ` Tom Rini
2004-01-21 19:21         ` Tom Rini
2004-01-21 19:22           ` Tom Rini
2004-01-22 17:44             ` Tom Rini
2004-01-22 18:05               ` Tom Rini [this message]
2004-01-23 22:46                 ` Tom Rini
2004-01-23 23:38                   ` George Anzinger
2004-01-26 20:46                     ` Tom Rini
2004-01-26 21:27                       ` George Anzinger
2004-01-26 21:42                         ` Tom Rini
2004-01-26 22:35                           ` George Anzinger
2004-01-26 21:45                       ` George Anzinger
2004-01-26 22:06                         ` Tom Rini
2004-01-27  9:05                           ` Amit S. Kale
2004-01-24  0:48                   ` George Anzinger
2004-01-24  3:47                   ` [PATCH] Kgdb dwarf2 for asm George Anzinger
2004-01-27 18:22                   ` PPC KGDB changes and some help? Tom Rini
2004-01-21 22:03           ` Tom Rini
2004-01-21 23:12           ` George Anzinger
2004-01-22 15:07             ` Tom Rini
2004-01-22 15:25               ` Hollis Blanchard
2004-01-22 15:45                 ` Tom Rini
2004-01-22 16:06                   ` Amit S. Kale
2004-01-22 16:45                     ` Tom Rini
2004-01-22 22:46                       ` George Anzinger
2004-01-22 22:52                         ` Tom Rini
2004-01-22 23:09                           ` George Anzinger
2004-01-22 22:35                     ` George Anzinger
2004-01-23 17:08                     ` Tom Rini
2004-01-22 21:54                   ` George Anzinger
2004-01-26 21:32           ` Tom Rini
2004-01-27  8:59             ` Amit S. Kale
2004-01-21 23:05         ` George Anzinger
2004-01-22 15:03           ` Tom Rini
2004-01-21 17:01     ` Amit S. Kale
2004-01-21 17:08       ` Tom Rini
2004-01-22  1:13   ` FYI: Free Online Book: Inside Linux Kernel and PowerPC Huailin Chen
2004-01-22 15:42     ` Hollis Blanchard
2004-01-22 18:43     ` URL: " Huailin Chen

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=20040122180555.GK15271@stop.crashing.org \
    --to=trini@kernel.crashing.org \
    --cc=amitkale@emsyssoft.com \
    --cc=george@mvista.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.