From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@zip.com.au>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [patch] kgdb light, v6
Date: Sun, 10 Feb 2008 23:24:59 +0100 [thread overview]
Message-ID: <200802102324.59821.bzolnier@gmail.com> (raw)
In-Reply-To: <20080210210900.GA27162@elte.hu>
On Sunday 10 February 2008, Ingo Molnar wrote:
[...]
> > > +__setup("kgdboc=", kgdboc_option_setup);
> >
> > no need for obsolete __setup, we have module_param_call() below
>
> it's needed for bzImage kernels. I just tested it and without __setup()
> no init sequence is run and KGDB is not activated.
weird, should work with "kgdboc.kgdboc=" parameter
[...]
> > > +#ifndef KGDB_MAX_BREAKPOINTS
> > > +# define KGDB_MAX_BREAKPOINTS 1000
> > > +#endif
> > > +
> > > +#define KGDB_HW_BREAKPOINT 1
> >
> > unused
>
> hm, both KGDB_MAX_BREAKPOINTS and KGDB_HW_BREAKPOINT are used.
my bad
[...]
> > if kgdb_isremovedbreak() helper is moved before kgdb_set_sw_break()
> > and converted to return 'i' on success and '-1' on failure then it can
> > be used instead the above for () loop
>
> dunno - that would complicate arch/x86/kernel/kgdb.c's use of
> kgdb_isremovedbreak() and looks a bit complex. If you feel strongly
the whole difference w.r.t. arch/x86/kernel/kgdb.c should be:
- if (exception == 3 && kgdb_isremovedbreak(regs->ip - 1)) {
+ if (exception == 3 && kgdb_isremovedbreak(regs->ip - 1) >= 0) {
> about it, could you send a patch?
well, maybe in the future if nobody fixes it :)
[ added as low-prio to my TODO... ]
Thanks for fixing all the other stuff.
Bart
next prev parent reply other threads:[~2008-02-10 22:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 7:13 [3/6] kgdb: core Ingo Molnar
2008-02-10 7:31 ` Sam Ravnborg
2008-02-10 7:59 ` Ingo Molnar
2008-02-10 7:35 ` Christoph Hellwig
2008-02-10 7:43 ` Ingo Molnar
2008-02-10 7:57 ` Christoph Hellwig
2008-02-10 8:02 ` Ingo Molnar
2008-02-10 8:21 ` Ingo Molnar
2008-02-10 8:26 ` Christoph Hellwig
2008-02-10 9:08 ` Ingo Molnar
2008-02-10 9:17 ` Ingo Molnar
2008-02-10 9:20 ` Ingo Molnar
2008-02-10 9:34 ` Ingo Molnar
2008-02-10 9:31 ` Christoph Hellwig
2008-02-10 17:17 ` [patch] kgdb light, v6 Ingo Molnar
2008-02-10 19:43 ` Bartlomiej Zolnierkiewicz
2008-02-10 21:31 ` Ingo Molnar
2008-02-10 20:55 ` Bartlomiej Zolnierkiewicz
2008-02-10 21:09 ` Ingo Molnar
2008-02-10 21:45 ` Jan Kiszka
2008-02-10 22:14 ` Bartlomiej Zolnierkiewicz
2008-02-10 22:32 ` Jan Kiszka
2008-02-10 22:40 ` Ingo Molnar
2008-02-11 2:35 ` Yinghai Lu
2008-02-10 22:31 ` Ingo Molnar
2008-02-10 22:24 ` Bartlomiej Zolnierkiewicz [this message]
2008-02-10 8:24 ` [3/6] kgdb: core Christoph Hellwig
2008-02-10 8:57 ` Ingo Molnar
2008-02-10 9:11 ` Christoph Hellwig
2008-02-10 9:27 ` Ingo Molnar
2008-02-10 9:34 ` Christoph Hellwig
2008-02-10 17:02 ` Ingo Molnar
2008-02-10 12:46 ` Marcin Slusarz
2008-02-10 13:19 ` Jesper Juhl
2008-02-10 14:00 ` Marcin Slusarz
2008-02-10 13:36 ` Jan Kiszka
2008-02-10 16:43 ` Ingo Molnar
2008-02-10 19:20 ` Bartlomiej Zolnierkiewicz
2008-02-10 16:46 ` Ingo Molnar
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=200802102324.59821.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=akpm@zip.com.au \
--cc=hch@infradead.org \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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