All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] kgdb: fixes and ARCH=arm support
Date: Thu, 21 Feb 2008 07:22:15 +0100	[thread overview]
Message-ID: <20080221062215.GA10172@elte.hu> (raw)
In-Reply-To: <1203536020-20102-1-git-send-email-jason.wessel@windriver.com>


* Jason Wessel <jason.wessel@windriver.com> wrote:

> Here are 3 more patches against the kgdb-light.  Porting kgdb-light to 
> another arch has found 2 regressions, which are fixed in the first 
> patch.
> 
> The second patch adds hooks for an additional kgdboc uart driver which 
> was required to complete the testing with real hardware.
> 
> The third patch adds the ARCH=arm support for kgdb-light.

thanks Jason. I've merged all 3 into the kgdb-light tree to ease 
testing.

I think we should also try to do some self-tests, so that when one boots 
a bzImage with the self-tests activated it can be said that all the 
basic functionality works. Simulated via some loopback method, from 
within the kernel - not via a real serial line - but it should have the 
capability to do real single-stepping and inject real hw breakpoints and 
test that they work. What do you think?

	Ingo

  parent reply	other threads:[~2008-02-21  6:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 19:33 [PATCH 0/3] kgdb: fixes and ARCH=arm support Jason Wessel
2008-02-20 19:33 ` [PATCH 1/3] kgdb: fix optional arch functions and probe_kernel_* Jason Wessel
2008-02-20 19:33   ` [PATCH 2/3] kgdb: kgdboc pl011 I/O module Jason Wessel
2008-02-20 19:33     ` [PATCH 3/3] kgdb: support for ARCH=arm Jason Wessel
2008-02-21  6:22 ` Ingo Molnar [this message]
2008-02-21 14:36   ` [PATCH 0/3] kgdb: fixes and ARCH=arm support Jason Wessel

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=20080221062215.GA10172@elte.hu \
    --to=mingo@elte.hu \
    --cc=jason.wessel@windriver.com \
    --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 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.