Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1653244
| From | Vlastimil Babka <vbabka.lkml@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability |
| Date | 2017-05-30 15:50 +0200 |
| Message-ID | <tMPH3-82d-7@gated-at.bofh.it> (permalink) |
| References | <tnn1E-xY-5@gated-at.bofh.it> <tnn1F-xY-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 03/21/2017 09:01 AM, Lu Baolu wrote: > XHCI debug capability (DbC) is an optional but standalone > functionality provided by an xHCI host controller. Software > learns this capability by walking through the extended > capability list of the host. XHCI specification describes > DbC in the section 7.6. > > This patch introduces the code to probe and initialize the > debug capability hardware during early boot. With hardware > initialized, the debug target (system on which this code is > running) will present a debug device through the debug port > (normally the first USB3 port). The debug device is fully > compliant with the USB framework and provides the equivalent > of a very high performance (USB3) full-duplex serial link > between the debug host and target. The DbC functionality is > independent of the xHCI host. There isn't any precondition > from the xHCI host side for the DbC to work. > > One use for this feature is kernel debugging, for example > when your machine crashes very early before the regular > console code is initialized. Other uses include simpler, > lockless logging instead of a full-blown printk console > driver and klogd. > > Cc: Ingo Molnar <mingo@redhat.com> > Cc: Mathias Nyman <mathias.nyman@linux.intel.com> > Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com> ... > + > +#define XDBC_TRACE > +#ifdef XDBC_TRACE > +#define xdbc_trace trace_printk Did you forget to remove the #define XDBC_TRACE? Enabling this driver brings the "trace_printk() being used. Allocating extra memory. This means that this is a DEBUG kernel and it is unsafe for production use." message in 4.12-rcX dmesg. Thanks, Vlastimil
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability Vlastimil Babka <vbabka.lkml@gmail.com> - 2017-05-30 15:50 +0200
Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability Lu Baolu <baolu.lu@linux.intel.com> - 2017-05-31 05:30 +0200
Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability Steven Rostedt <rostedt@goodmis.org> - 2017-05-31 08:30 +0200
Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability Lu Baolu <baolu.lu@linux.intel.com> - 2017-06-01 05:40 +0200
Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability Vlastimil Babka <vbabka@suse.cz> - 2017-05-31 11:40 +0200
Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability Lu Baolu <baolu.lu@linux.intel.com> - 2017-06-01 05:40 +0200
Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability Vlastimil Babka <vbabka@suse.cz> - 2017-06-01 10:20 +0200
Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability Peter Zijlstra <peterz@infradead.org> - 2017-06-01 14:30 +0200
Re: [PATCH v8 2/5] usb: early: add driver for xhci debug capability Steven Rostedt <rostedt@goodmis.org> - 2017-06-02 02:50 +0200
csiph-web