linux-kernel - Re: [PATCH 0/2] small xhci cleanups

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] [day] [month] [year] [list]

Date:	Thu, 18 Mar 2010 15:54:32 -0700
From:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
To:	Greg KH <greg@...ah.com>
Cc:	Alex Chiang <achiang@...com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] small xhci cleanups

On Thu, Mar 18, 2010 at 03:19:58PM -0700, Greg KH wrote:
> On Thu, Mar 18, 2010 at 02:33:08PM -0700, Sarah Sharp wrote:
> > Yes, I did par down the duplicate/redundant messages, but I still want
> > to see very detailed messages when I think there's a hardware problem.
> > 
> > What if I removed the debug config option for xHCI, allowed people to
> > use dynamic debugging to enable debugging for specific xHCI files, but
> > also allowed them to set the log level through a debugfs file?  That way
> > people could still control the variety of messages that they see, but
> > they can also change the level of debugging dynamically.
> 
> Sure, that might work, but I'd recommend tracing for the most part,
> that's what it is there for :)

Ok, I'll look into adding trace events.

Sarah Sharp
--
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/