Date: Fri, 6 Nov 1998 15:57:35 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: "Kenneth D. Merry" <ken@plutotech.com> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAMDEBUG change to mull over... Message-ID: <Pine.LNX.4.02.9811061556230.3059-100000@feral-gw> In-Reply-To: <199811062353.QAA03708@panzer.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. > There are two things desired: one is files/modules. There is per-device. Well, we can discuss it until the cows come home. Why don't I hack for a while and if something seems of general use, I'll propose it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.02.9811061556230.3059-100000>