public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kgdb over ethernet?
Date: Fri, 25 Apr 2008 12:32:39 -0500	[thread overview]
Message-ID: <481215B7.9020503@windriver.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0804251837410.20150@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> Hi,
>
>
> the DocBook files for the recently-merged kgdb mention kgdboe, as does 
> the doc on kgdb.sf.net, but I do not see kgdboe anywhere in the source. 
> Is oe actually merged? I'm kinda short on rs232...
>   
Well if you have at least one you have enough because you can share kgdb
with the console.

> thanks,
> Jan
>   

kgdboe is not in the mainline kernel. 

It is a feature that might end up being re-implemented at some point or
perhaps merged as is in the future.  The current kgdboe suffers from
some reliability problems related to the need to sync interrupts prior
to using the network device hardware.  This is due to the way the
"polled mode" support is implemented in the NET POLL API.  There is
presently no good means to avoid certain deadlock scenarios.

That being said if you want to work with the latest kgdb + the latest
kernel work it is available.  First you clone Linus's tree and then do
something like:

git remote add kgdb-next
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git
git remote update
git checkout kgdb-next

And later when if you update it, you would want make sure and use the
"+" type pull because the branch gets shuffled quite often with patches
pulled in and out of the tree.  IE:

git pull kgdb-next +kgdb-next:kgdb-next

Jason.

  reply	other threads:[~2008-04-25 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25 16:39 kgdb over ethernet? Jan Engelhardt
2008-04-25 17:32 ` Jason Wessel [this message]
2008-04-26 14:30   ` Stefan Richter
2008-04-26 15:03     ` Jan Engelhardt
2008-04-26 15:30   ` Jan Engelhardt
2008-04-28 13:34     ` 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=481215B7.9020503@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=jengelh@computergmbh.de \
    --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