linux-kernel - Re: [PATCH 1/6] GenWQE PCI support, health monitoring and recovery

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131203143036.GC3521@kroah.com>
Date:	Tue, 3 Dec 2013 06:30:36 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Frank Haverkamp <haver@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, arnd@...db.de,
	cody@...ux.vnet.ibm.com, schwidefsky@...ibm.com,
	utz.bacher@...ibm.com, mmarek@...e.cz, rmallon@...il.com,
	jsvogt@...ibm.com, MIJUNG@...ibm.com, cascardo@...ux.vnet.ibm.com,
	michael@...ra.de
Subject: Re: [PATCH 1/6] GenWQE PCI support, health monitoring and recovery

On Tue, Dec 03, 2013 at 02:49:41PM +0100, Frank Haverkamp wrote:
> Hi Greg,
> 
> Am Mittwoch, den 27.11.2013, 11:20 -0800 schrieb Greg KH:
> > On Wed, Nov 06, 2013 at 01:45:38PM +0100, Frank Haverkamp wrote:
> > > +/*
> > > + * Flags for extended output (dbg_print)
> > > + *   We define different levels of debugging for the appropriate unit.
> > > + */
> > > +#define dbg_card			0x00000001
> > > +#define dbg_card_ddcb			0x00000004
> > > +#define dbg_card_regs			0x00000008
> > > +#define dbg_card_sglist			0x00000400
> > > +#define dbg_card_pinning		0x00000800
> > > +
> > > +#define genwqe_dprintk(_cd, dbg_unit, fmt, ...) do {			\
> > > +		struct genwqe_dev *__cd = (_cd);			\
> > > +		if ((_cd)->debug & (dbg_unit))				\
> > > +			dev_info(&__cd->pci_dev->dev, fmt,		\
> > > +				 ## __VA_ARGS__);			\
> > > +	} while (0)
> > 
> > Ugh, really?  How is a debugging printk being sent out with dev_info()?
> > 
> > And why not just use dynamic kernel debugging and not create your own
> > masks and macros?  We are trying to make everything use the same
> > infrastructure, please don't create new ones for every individual driver
> > in the kernel, that's a mess.
> 
> I removed the genwqe_dprintk function completely. Our debug flag I kept
> for the moment, because I like to use the kernel hexdump functions to
> print my control blocks for debugging:
> 
>       if (cd->debug & dbg_card_ddcb) {
>              dev_dbg(&pci_dev->dev, "FINISHED DDCB#%d\n", req->num);
>              genwqe_hexdump(pci_dev, pddcb, sizeof(*pddcb));
>       }
> 
> Or is there something allowing me to do those hexdumps with the
> dynamic_debug feature too? dynamic_hex_dump() looks like what I want.

Yes, that is what to use.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/