All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Prakash, Sathya" <sathya.prakash@lsi.com>
Cc: linux-scsi@vger.kernel.org, eric.moore@lsi.com
Subject: Re: [PATCH 0/5] mpt fusion: Add logging support
Date: Fri, 27 Jul 2007 12:21:12 -0400	[thread overview]
Message-ID: <1185553272.3655.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20070724100659.GA1831@lsil.com>

On Tue, 2007-07-24 at 15:36 +0530, Prakash, Sathya wrote:
> The patches in this patch set adds support for logging facility that can be used
> to debug a number of Fusion MPT related problems.
> 
> The logging support can be enabled or disabled changing the kernel
> configuration flag CONFIF_FUSION_LOGGING
> 
> The debug level can be programmed on the fly via SysFS (hex values)
> 	echo [level] > /sys/class/scsi_host/host#/debug_level
> and also can be passed as module parameter mpt_debug_level for mptbase.ko

The way your module parameter works is slightly counter intuitive.  On
all our other drivers, you can write a value into 

/sys/module/<module>/parameters/<debug parameter>

And have it acted on immediately.  In yours, it seems only to work
before the host is probed (because after that, the value in the ioc
structure is what's used).

The other question is are you really sure you actually want per host
debugging?  is the added flexibility in being able to turn it on and off
per host worth the problems of explaining to the users where to find the
parameter?  I've got to bet that 95% of the installations only have a
single fusion card anyway.  would it not be simpler just to have a
global module parameter that can be set and acted on from /sys/modules?

James



  parent reply	other threads:[~2007-07-27 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 10:06 [PATCH 0/5] mpt fusion: Add logging support Prakash, Sathya
2007-07-26 16:37 ` Moore, Eric
2007-07-27 16:21 ` James Bottomley [this message]
2007-07-27 22:16   ` Moore, Eric
2007-07-27 22:30     ` James Bottomley
2007-07-28 17:40       ` James Bottomley
2007-07-30 18:33         ` Moore, Eric
2007-07-30 22:31           ` FUJITA Tomonori
2007-07-31 18:40             ` Moore, Eric
2007-08-01 21:57               ` FUJITA Tomonori
2007-07-28  4:14     ` Mr. James W. Laferriere

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1185553272.3655.22.camel@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=eric.moore@lsi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sathya.prakash@lsi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.