Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263598AbUANGcr (ORCPT ); Wed, 14 Jan 2004 01:32:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263221AbUANGcr (ORCPT ); Wed, 14 Jan 2004 01:32:47 -0500 Received: from waste.org ([209.173.204.2]:19406 "EHLO waste.org") by vger.kernel.org with ESMTP id S263598AbUANGcq (ORCPT ); Wed, 14 Jan 2004 01:32:46 -0500 Date: Wed, 14 Jan 2004 00:31:55 -0600 From: Matt Mackall To: George Anzinger Cc: "Amit S. Kale" , Andrew Morton , jim.houston@comcast.net, discuss@x86-64.org, ak@suse.de, shivaram.upadhyayula@wipro.com, lkml , Pavel Machek Subject: Re: [discuss] Re: kgdb for x86_64 2.6 kernels Message-ID: <20040114063155.GF28521@waste.org> References: <000e01c3d476$2ebe03a0$4008720a@shivram.wipro.com> <200401101611.53510.amitkale@emsyssoft.com> <400237F0.9020407@mvista.com> <200401122020.08578.amitkale@emsyssoft.com> <40046296.1050702@mvista.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40046296.1050702@mvista.com> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1629 Lines: 29 On Tue, Jan 13, 2004 at 01:26:46PM -0800, George Anzinger wrote: > > > >Serial interface should be configurable independent of kgdb and may not be > >configured if ethernet interface is configured. Serial interface is far > >simpler hence superior for debugging purposes. If it's available, using > >ethernet interface is out of question. Ethernet interface can be used when > >serial hardware isn't present or is being used for some other purposes. > > > I rather think that the serial inteface should be the fall back unless the > user has told us at configure time that it is not available. I am not > prepared to make a statment that it is better than eth. The eth intface > should be much faster, but it has its fingers into a large part of the > kernel that MAY be the subject of the current session. Thus, I think that > eth may be better, IF one is clearly not involved in debugging those areas > of the kernel. (Which, by the way, we need to enumerate at some point.) I have in mind creating some other interfaces that will be on a par with serial for early boot availability. So lets not frame this in terms of eth vs serial. We can throw a priority int in the config interface, stuff that in the plug struct, and pick whichever one's highest and claims to be currently available. -- Matt Mackall : http://www.selenic.com : Linux development and consulting - 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/