linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurence Oberman <loberman@redhat.com>
To: "Kai Mäkisara (Kolumbus)" <kai.makisara@kolumbus.fi>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH]: add debug flag parameter for SCSI tape driver
Date: Wed, 11 Jun 2014 14:24:25 -0400 (EDT)	[thread overview]
Message-ID: <664697763.17697275.1402511065048.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1CAC495F-3A9A-45B1-8E15-4B6D3F17114D@kolumbus.fi>

Kai,
Thank you for considering this.

With #define DEBUG 0
We still include

#define DEB(a)
#define DEBC(a)

With the debug_flag we then provide the needed debug I am looking for at module load time.
But I agree that it enables it for all devices and that may not be optimal
I don't change the default, I just allow the parameter to control it.

In the last few issues I have been working I have had to recompile and provide the st module to get what I needed captured for debugging so I decided to try the patch submission.

Thank You
Laurence

----- Original Message -----
From: "Kai Mäkisara (Kolumbus)" <kai.makisara@kolumbus.fi>
To: "Laurence Oberman" <loberman@redhat.com>
Cc: linux-scsi@vger.kernel.org
Sent: Wednesday, June 11, 2014 2:03:15 PM
Subject: Re: [PATCH]: add debug flag parameter for SCSI tape driver


On 11.6.2014, at 2.48, Laurence Oberman <loberman@redhat.com> wrote:

> Hello
> 
> Take 2 of this patch, changed module description and subject line.
> 
> This patch adds a debug_flag parameter that can be set on module load, and allows the DEBUG facility without a module recompile.
> Usage: mpdprobe st debug_flag=1
> 
> Signed-off-by: Laurence Oberman <loberman@redhat.com>
> 

What is wrong with the existing methods to control debugging? You can enable and disable debugging for each device with ioctl() (as described in the driver documentation). You can use mt-st to do this from command line.

Your patch just allows one to change the default for all devices. The real problem may be that the distributions don’t compile the debugging code into the drivets but your patch does not change this.

Kai

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-06-11 18:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2027096335.17236699.1402433423338.JavaMail.zimbra@redhat.com>
2014-06-10 20:51 ` Debug flag parameter for SCSI tape driver Laurence Oberman
2014-06-10 23:48   ` [PATCH]: add debug " Laurence Oberman
2014-06-11 18:03     ` "Kai Mäkisara (Kolumbus)"
2014-06-11 18:24       ` Laurence Oberman [this message]
2014-06-11 19:35         ` Dale R. Worley
2014-06-11 19:54         ` Laurence Oberman
2014-06-13 21:18           ` Debug " Dale R. Worley
2014-10-17 20:20       ` [PATCH]: add debug flag parameter for SCSI tape driver - 2nd request Laurence Oberman
2014-10-17 20:41         ` Laurence Oberman
2014-10-19  8:54         ` "Kai Mäkisara (Kolumbus)"
2014-10-19 13:44           ` Laurence Oberman
2014-10-19 19:37             ` "Kai Mäkisara (Kolumbus)"
2014-10-23 17:11             ` Christoph Hellwig

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=664697763.17697275.1402511065048.JavaMail.zimbra@redhat.com \
    --to=loberman@redhat.com \
    --cc=kai.makisara@kolumbus.fi \
    --cc=linux-scsi@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).