Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755054Ab2HTUvi (ORCPT ); Mon, 20 Aug 2012 16:51:38 -0400 Received: from mail-lb0-f174.google.com ([209.85.217.174]:56539 "EHLO mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752117Ab2HTUvf (ORCPT ); Mon, 20 Aug 2012 16:51:35 -0400 MIME-Version: 1.0 In-Reply-To: <20120820144449.GA32560@lizard> References: <20120820144449.GA32560@lizard> Date: Mon, 20 Aug 2012 13:51:33 -0700 Message-ID: Subject: Re: [PATCH v4 0/12] KGDB/KDB FIQ (NMI) debugger From: Brian Swetland To: Anton Vorontsov Cc: Russell King , Jason Wessel , Greg Kroah-Hartman , Alan Cox , =?UTF-8?B?QXJ2ZSBIasO4bm5ldsOlZw==?= , Colin Cross , John Stultz , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linaro-kernel@lists.linaro.org, patches@linaro.org, kernel-team@android.com, kgdb-bugreport@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1925 Lines: 38 On Mon, Aug 20, 2012 at 7:44 AM, Anton Vorontsov wrote: > > - KGDB/KDB FIQ debugger shell is synchronous. In Google's version you > could have a dedicated shell always running in the FIQ context, so > when you type something on a serial line, you won't actually cause any > debugging actions, FIQ would save the characters in its own buffer and > continue execution normally. But when you hit return key after the > command, then the command is executed. > > In KGDB/KDB FIQ debugger it is different. Once you enter KGDB, the > kernel will stop until you instruct it to continue. > > This might look as a drastic change, but it is not. There is actually > no difference whether you have sync or async shell, or at least I > couldn't find any use-case where this would matter at all. Anyways, it > is still possible to do async shell in KDB, just don't see any need > for this. The main reason we did this asynchronously was that it's entirely possible to get the occasional random character on the debug serial port (which is often multiplexed with the audio path on the headphone jack), and having the device freeze mysteriously when this happens is problematic. Since the FIQ debugger is incredibly useful for diagnosing "my device is stuck" type problems, we tend to leave it enabled on large numbers of devices during internal testing, so that if somebody runs into a problem an engineer can plug in a serial debug cable and take a look. It's important that the presence of the debug feature doesn't lead to instability, and thus we don't want a single random character to stop the normal operation ofthe device. Brian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/