From: Ingo Molnar <mingo@kernel.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
tglx@linutronix.de, peterz@infradead.org,
linux-usb@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH v5 0/4] usb: early: add support for early printk through USB3 debug port
Date: Thu, 19 Jan 2017 10:12:02 +0100 [thread overview]
Message-ID: <20170119091202.GB22865@gmail.com> (raw)
In-Reply-To: <1479189731-2728-1-git-send-email-baolu.lu@linux.intel.com>
* Lu Baolu <baolu.lu@linux.intel.com> wrote:
> xHCI debug capability (DbC) is an optional but standalone
> functionality provided by an xHCI host controller. With DbC
> hardware initialized, the system will present a debug device
> through the USB3 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 xHCI host. There
> isn't any precondition from xHCI host side for DbC to work.
>
> This patch set adds support for early printk functionality
> through a USB3 debug port by 1) initializing and enabling
> the DbC hardware during early boot; 2) registering a boot
> console to the system so that early printk messages can go
> through the USB3 debug port. It also includes some lines
> of changes in usb_debug driver so that it can be bound when
> a USB3 debug device is enumerated.
>
> This code is designed to be used only for kernel debugging
> when machine crashes very early before the console code is
> initialized. It makes the life of kernel debugging easier
> when people work with a modern machine without any legacy
> serial ports.
BTW., just a side note, some kernel developers (like PeterZ - and I do it
sometimes too) remap early_printk to printk permanently and use it as their main
printk facility - because printk() reliability has suffered over the last couple
of years.
So it's more than just early boot debugging - it's a very simple state-less
logging facility to an external computer.
Thanks,
ngo
next prev parent reply other threads:[~2017-01-19 9:12 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 6:02 [PATCH v5 0/4] usb: early: add support for early printk through USB3 debug port Lu Baolu
2016-11-15 6:02 ` [PATCH v5 1/4] usb: dbc: early driver for xhci debug capability Lu Baolu
2017-01-19 9:37 ` Ingo Molnar
2017-01-20 2:47 ` Lu Baolu
2017-01-22 9:04 ` Ingo Molnar
2017-01-24 4:44 ` Lu Baolu
2017-01-24 8:20 ` Ingo Molnar
2017-01-25 5:28 ` Lu Baolu
2017-01-25 9:23 ` Ingo Molnar
2017-01-25 9:57 ` Peter Zijlstra
2017-01-25 12:27 ` Lu Baolu
2017-01-25 14:38 ` Peter Zijlstra
2017-01-25 15:51 ` Lu Baolu
2017-01-25 16:16 ` Peter Zijlstra
2017-01-26 3:37 ` Lu Baolu
2017-01-26 7:19 ` Ingo Molnar
2017-01-26 7:49 ` Lu Baolu
2017-01-26 8:17 ` Ingo Molnar
2017-01-26 10:28 ` Peter Zijlstra
2017-01-26 16:01 ` Ingo Molnar
2017-01-26 17:39 ` Peter Zijlstra
2017-01-27 6:51 ` Ingo Molnar
2017-02-09 5:59 ` Lu Baolu
2017-01-26 7:22 ` Ingo Molnar
2017-02-09 7:37 ` Lu Baolu
2017-01-25 12:17 ` Lu Baolu
2017-01-26 3:26 ` Lu Baolu
2016-11-15 6:02 ` [PATCH v5 2/4] x86: add support for earlyprintk via USB3 debug port Lu Baolu
2017-01-19 9:38 ` Ingo Molnar
2017-01-20 2:48 ` Lu Baolu
2016-11-15 6:02 ` [PATCH v5 3/4] usb: serial: usb_debug: add support for dbc debug device Lu Baolu
2017-01-19 9:39 ` Ingo Molnar
2017-01-20 2:50 ` Lu Baolu
2016-11-15 6:02 ` [PATCH v5 4/4] usb: doc: add document for USB3 debug port usage Lu Baolu
2017-01-19 9:41 ` Ingo Molnar
2017-01-20 2:53 ` Lu Baolu
2017-01-18 6:20 ` [PATCH v5 0/4] usb: early: add support for early printk through USB3 debug port Lu Baolu
2017-01-19 9:06 ` Greg Kroah-Hartman
2017-01-19 9:09 ` Ingo Molnar
2017-01-19 11:24 ` Mathias Nyman
2017-01-19 9:12 ` Ingo Molnar [this message]
2017-01-20 2:56 ` Lu Baolu
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=20170119091202.GB22865@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=baolu.lu@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.