Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 24 Feb 2020 12:03:26 +0000
From:   Daniel Thompson <daniel.thompson@linaro.org>
To:     Jordan Hand <jorhand@linux.microsoft.com>
Cc:     netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
        jason.wessel@windriver.com, dianders@chromium.org
Subject: Re: net/kgdb: Taking another crack at implementing kgdboe
Message-ID: <20200224120326.igxombbpuiqrjucx@holly.lan>
References: <ccd03920-375a-2e65-cc28-d00f3297cb67@linux.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ccd03920-375a-2e65-cc28-d00f3297cb67@linux.microsoft.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Feb 21, 2020 at 04:33:48PM -0800, Jordan Hand wrote:
> Hey folks,
> 
> I have been scouring patches from around 2005-2008 related to kgdboe
> (kgdb over ethernet) and I am interested in taking a shot at getting it
> into the mainline kernel.
> 
> I found an implementation from Tom Rini in 2005[1] and an out of tree
> implementation[2].
> 
> So I have a couple questions before I dive in:
> 
> 1. Is anyone actively working on this? From lkml archives it appears no
> but I thought I'd ask.
> 2. Does anyone have an objection to this feature? From my reading it
> seems that the reason it was never merged was due to reliability issues
> but I just want to double check that people don't see some larger issue.

Like Jason said, I can't see any objections on the kgdb side but
integrating even with simple peripherals (UARTs for example) has it's
share of pitfalls so it may take a fair bit of work to make the net
developers comfortable!


Daniel.