From: Andi Kleen <andi@firstfloor.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net,
Peter Zijlstra <peterz@infradead.org>,
mingo@elte.hu, mort@sgi.com, linux-arch@vger.kernel.org
Subject: Re: [PATCH 05/37] kdb: core for kgdb back end
Date: Tue, 29 Dec 2009 00:37:34 +0100 [thread overview]
Message-ID: <20091228233734.GA15175@basil.fritz.box> (raw)
In-Reply-To: <4B3932D3.8020608@windriver.com>
On Mon, Dec 28, 2009 at 04:36:03PM -0600, Jason Wessel wrote:
> Andi Kleen wrote:
> > Jason Wessel <jason.wessel@windriver.com> writes:
> >
> > I remember going with kaos through all the code
> > outside kdb/ in his own patch and for nearly all hooks
> > outside we found some way to eliminate them.
> >
> > I think a lot of this is here too.
>
>
> If this has been solved before somewhere, please point me in that direction. There are whole lot few changes in this series vs original kdb outside of the kdb core area.
I don't think we ever generated patches, just reviewed all the changes
outside kdb/* and eventually agreed that it wasn't needed or could be done in a much
cleaner way.
Frankly some things can be also just dropped. Or if you're really desperate
about nops just nop the spinlock functions while kdb runs.
-Andi
next prev parent reply other threads:[~2009-12-28 23:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1261603190-5036-1-git-send-email-jason.wessel@windriver.com>
[not found] ` <1261603190-5036-2-git-send-email-jason.wessel@windriver.com>
[not found] ` <1261603190-5036-3-git-send-email-jason.wessel@windriver.com>
[not found] ` <1261603190-5036-4-git-send-email-jason.wessel@windriver.com>
[not found] ` <1261603190-5036-5-git-send-email-jason.wessel@windriver.com>
2009-12-23 21:19 ` [PATCH 05/37] kdb: core for kgdb back end Jason Wessel
2009-12-24 1:28 ` Andi Kleen
2009-12-28 22:36 ` Jason Wessel
2009-12-28 23:37 ` Andi Kleen [this message]
2009-12-24 11:01 ` Peter Zijlstra
2009-12-24 11:16 ` Peter Zijlstra
2009-12-24 15:57 ` Jason Wessel
2009-12-26 21:34 ` Mike Frysinger
2009-12-24 11:55 ` Jason Wessel
2009-12-24 11:55 ` Jason Wessel
2009-12-24 12:01 ` Peter Zijlstra
2009-12-24 11:04 ` Peter Zijlstra
2009-12-28 16:33 ` Jason Wessel
2009-12-28 16:55 ` Peter Zijlstra
2009-12-28 17:15 ` 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=20091228233734.GA15175@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mort@sgi.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).