From: Randy Dunlap <randy_d_dunlap@linux.intel.com>
To: Tejun Heo <htejun@gmail.com>
Cc: bbpetkov@yahoo.de, jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: PATCH convert libata-core to the new debugging scheme
Date: Tue, 24 Jan 2006 08:30:23 -0800 [thread overview]
Message-ID: <20060124083023.14df7ce0.randy_d_dunlap@linux.intel.com> (raw)
In-Reply-To: <43D626D6.60507@gmail.com>
On Tue, 24 Jan 2006 22:08:38 +0900
Tejun Heo <htejun@gmail.com> wrote:
> Borislav Petkov wrote:
> > On Tue, Jan 17, 2006 at 10:57:02AM -0800, Randy Dunlap wrote:
> > Hi Jeff, Randy,
> >
> > here's a rehash against 2.6.16-rc1 of the 2nd patch I sent then but it somehow
> > got lost along the way. It converts the libata-core.c to the new debugging scheme.
> >
> > Problem: In the ata_dev_classify() function we don't have access to an
> > ata_host struct probably because we're still probing so maybe we'll have to
> > print debugging statements in a different manner. Same for early init
> > routines like ata_device_add(), ata_probe_ent_alloc(), ata_pci_init_one().
> >
> > Also, Jeff, if you'd still like to have a way of setting/getting debugging
> > levels from userspace, please elaborate more on that so that I have some
> > directions (ioctl, proc, etc).
>
> I'm not Jeff, but my 5 Won (that's like half a cent) would be on sysfs.
> People hate ioctl and proc these days.
>
> >
> > Thanks,
> > Boris.
> >
> > p.s. Please CC me since I'm not subscribed to the linux-ide ML.
> >
> > Signed-off-by: Borislav Petkov <petkov@uni-muenster.de>
> >
> >
> > --- 16-rc1/drivers/scsi/libata-core.c.orig 2006-01-21 09:42:53.000000000 +0100
> > +++ 16-rc1/drivers/scsi/libata-core.c 2006-01-24 09:58:00.000000000 +0100
> > @@ -115,13 +115,15 @@ static void ata_tf_load_pio(struct ata_p
> > outb(tf->hob_lbal, ioaddr->lbal_addr);
> > outb(tf->hob_lbam, ioaddr->lbam_addr);
> > outb(tf->hob_lbah, ioaddr->lbah_addr);
> > - VPRINTK("hob: feat 0x%X nsect 0x%X, lba 0x%X 0x%X 0x%X\n",
> > - tf->hob_feature,
> > - tf->hob_nsect,
> > - tf->hob_lbal,
> > - tf->hob_lbam,
> > - tf->hob_lbah);
> > - }
> > + if (ata_msg_ctl(ap))
> > + printk(KERN_DEBUG "%s: hob: feat 0x%X nsect 0x%X, lba 0x%X 0x%X 0x%X\n",
> > + __FUNCTION__,
> > + tf->hob_feature,
> > + tf->hob_nsect,
> > + tf->hob_lbal,
> > + tf->hob_lbam,
> > + tf->hob_lbah);
> > + }
>
> Wouldn't it be better to wrap 'if (ata_msg_ctl(ap)) printk' into some
> pretty macro? Debug messages tend to be long and 8 characters can be
> used better. IMHO, 'if' clauses for debug messages lower readability a bit.
I agree that a wrapper would be nice.
Without a wrapper (in this current patch), I see some (new) lines
that are indented too much, e.g.:
if (ata_msg_err(ap))
printk(KERN_WARNING "%s: ata%u: PIO error\n", __FUNCTION__, ap->id);
Secondly, we usually try to make source lines fit into 80
columns, so using a line break after the first comma would be
Good.
Both of these points apply to multiple places in the patch.
And here:
- DPRINTK("init dev params \n");
+ if (ata_msg_ctl(ap))
+ printk(KERN_DEBUG "%s: init dev params \n", __FUNCTION__);
Drop the space after "params".
Anyway, back to the more important point. How can we make
this more compact (Tejun's wrapper recommendation)?
Maybe something like (when <ap> is available):
#define ATA_MSG_CTL(ap, fmt, args) \
do { if (ata_msg_ctl(ap)) \
printk(KERN_DEBUG "%s: " fmt, \
__FUNCTION__, ## args); \
} while(0)
or for "?:" fans like me, prints even when <ap> is NULL:
#define ATA_MSG_CTL(ap, fmt, args) \
do { if (ap ? ata_msg_ctl(ap) : 1) \
printk(KERN_DEBUG "%s: " fmt, \
__FUNCTION__, ## args); \
} while(0)
---
~Randy
next prev parent reply other threads:[~2006-01-24 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060117105702.5e5a5cb5.randy_d_dunlap@linux.intel.com>
2006-01-24 9:07 ` PATCH convert libata-core to the new debugging scheme Borislav Petkov
2006-01-24 13:08 ` Tejun Heo
2006-01-24 16:30 ` Randy Dunlap [this message]
2006-01-24 19:43 Borislav Petkov
2006-01-24 19:47 ` Jeff Garzik
2006-01-25 15:04 ` Bartlomiej Zolnierkiewicz
2006-01-25 15:06 ` Jeff Garzik
2006-01-25 15:13 ` Jens Axboe
2006-01-25 15:12 ` Jeff Garzik
2006-01-25 15:16 ` Jens Axboe
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=20060124083023.14df7ce0.randy_d_dunlap@linux.intel.com \
--to=randy_d_dunlap@linux.intel.com \
--cc=bbpetkov@yahoo.de \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).