From owner-freebsd-scsi Fri Nov 6 15:54:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24278 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 15:54:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24273 for ; Fri, 6 Nov 1998 15:54:12 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA03708; Fri, 6 Nov 1998 16:53:57 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811062353.QAA03708@panzer.plutotech.com> Subject: Re: CAMDEBUG change to mull over... In-Reply-To: from Matthew Jacob at "Nov 6, 98 12:15:12 pm" To: mjacob@feral.com Date: Fri, 6 Nov 1998 16:53:57 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > On Fri, 6 Nov 1998, Kenneth D. Merry wrote: > > That's not surprising at all. :) > > > > > What do you think about CAM_DEBUG_XPT flag that will allow this > > > to be traced separate from other tracing? > > > > Well, we could do that, but I'd rather have a little more generic solution > > that would allow turning on/off tracing for various modules or drivers. > > > > I.e., have something that would let you just turn on tracing for the sa > > driver, or just for the transport layer, or just for the error recovery > > code in cam_periph.c/scsi_all.c, or for all modules... > > > Well- if this is the case, let's nuke CAM_DEBUG_PRINT (at least as it is > currently used in cam_xpt.c- it really has to be used only sparingly or > you'll never be able to find this debugging any use at all) and allow a > set of arbitrary cam paths to used for debugging being enabled. The xpt > layer itself has a path (CAM_XPT_PATH_ID). I think it's fine to trim down the number of CAM_DEBUG_PRINT statements in cam_xpt.c. The transport layer path is -1, which is also used to turn on debugging for all busses. I'd rather come up with something separate from cam_path statements to specify which files/modules you want debugging info from. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message