public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Anurekh Saxena <anurekh.saxena@timesys.com>
Cc: "Amit S. Kale" <amitkale@emsyssoft.com>,
	kgdb-bugreport@lists.sourceforge.net,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Kgdb-bugreport] kgdb_arch_set/remove_break() ?
Date: Wed, 24 Mar 2004 14:40:29 -0700	[thread overview]
Message-ID: <20040324214029.GL7126@smtp.west.cox.net> (raw)
In-Reply-To: <20040324202402.GA20260@timesys.com>

On Wed, Mar 24, 2004 at 03:24:02PM -0500, Anurekh Saxena wrote:

> 
> On Wed, Mar 24, 2004 at 08:05:21PM +0530, Amit S. Kale wrote:
> > On Friday 19 Mar 2004 9:33 pm, Tom Rini wrote:
> > > Hi.  Right now I'm writing up a porting doc that describes the various
> > > hook functions we've got.  I noticed that nothing is calling
> > > kgdb_arch_set/remove_break.  Is there some arch we're expecting will
> > > need this?  I'd like to just go ahead and remove them
> > 
> > I can't remember why that was done. A processor other than PPC, x86 and x86_64 
> > needs a special implementation of set and remove breakpoint, I guess.
> > 
> > Anurekh, who did initial implementation of arch independent-dependent split 
> > may have some comments on this.
> 
> *set_break
> *remove_break
> 
> These functions should only be defined for architecutes that support
> hardware breakpoint. Set KGDB_HW_BREAKPOINT flag.

Amit, I think we've got a bug on i386 then.  Looking at i386-lite.patch,
there's:
+void kgdb_correct_hw_break(void)
+int kgdb_remove_hw_break(unsigned long addr, int type)
+int kgdb_set_hw_break(unsigned long addr, int type)
+int remove_hw_break(unsigned breakno)
+int set_hw_break(unsigned breakno, unsigned type, unsigned len, unsigned addr)

Of these, only kgdb_correct_hw_break is called in core-lite.patch, and
set_hw_break/remove_hw_break (for y/Y packets) are called in
i386-lite.patch.

What I think we need to do is, since y/Y packets are reserved, I'm
assuming there's a special version of GDB using these for hw
breakpoints, and this needs to be handled in i386-lite.patch.
Since core-lite's handling of a z/Z* packet is to assume setting a
breakpoint, and hw or sw is controlled by the KGDB_HW_BREAKPOINT flag,
we need to make sure this (a) works and (b) is actually calling useful
functions.

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

  reply	other threads:[~2004-03-24 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19 16:03 kgdb_arch_set/remove_break() ? Tom Rini
2004-03-24 14:35 ` [Kgdb-bugreport] " Amit S. Kale
2004-03-24 20:24   ` Anurekh Saxena
2004-03-24 21:40     ` Tom Rini [this message]
     [not found]       ` <200403251554.39598.amitkale@emsyssoft.com>
2004-03-25 19:37         ` Tom Rini

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=20040324214029.GL7126@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=amitkale@emsyssoft.com \
    --cc=anurekh.saxena@timesys.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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