From: Peter Zijlstra <peterz@infradead.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>,
linux-usb@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2 1/4] usb: dbc: early driver for xhci debug capability
Date: Wed, 19 Oct 2016 15:09:43 +0200 [thread overview]
Message-ID: <20161019130943.GA3175@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1476836305-4468-2-git-send-email-baolu.lu@linux.intel.com>
On Wed, Oct 19, 2016 at 08:18:22AM +0800, Lu Baolu wrote:
> +++ b/drivers/usb/early/xhci-dbc.c
> +static int xdbc_bulk_write(const char *bytes, int size)
> +{
> + unsigned long flags;
> + int ret, timeout = 0;
> +
> + spin_lock_irqsave(&xdbc.lock, flags);
Yikes!!
So how is this supposed to work from NMI context and the like?
(also, at the very least, that should be a raw_spinlock_t)
What do you need the spinlock for? Afaict this is a 'simple' polling
event handling loop on MMIO, right?
All we really need to guarantee is that there's only a single CPU trying
to do that at any one time.
Wouldn't something like:
https://marc.info/?l=linux-kernel&m=147681099108509&w=2
already take care of that? Then you can drop the lock and things will
work 'nested'.
> +
> + xdbc_handle_events();
> +
> + /* Check completion of the previous request. */
> + while (xdbc.flags & XDBC_FLAGS_OUT_PROCESS) {
> + if (timeout > 1000000)
> + break;
> +
> + spin_unlock_irqrestore(&xdbc.lock, flags);
> + xdbc_delay(100);
> + spin_lock_irqsave(&xdbc.lock, flags);
> + timeout += 100;
> +
> + xdbc_handle_events();
> + }
> +
> + if (xdbc.flags & XDBC_FLAGS_OUT_PROCESS) {
> + spin_unlock_irqrestore(&xdbc.lock, flags);
> +
> + /*
> + * Oops, hardware wasn't able to complete the
> + * previous transfer.
> + */
> + xdbc_trace("oops: previous transfer not completed yet\n");
> +
> + return -ETIMEDOUT;
> + }
> +
> + ret = xdbc_bulk_transfer((void *)bytes, size, false);
> +
> + spin_unlock_irqrestore(&xdbc.lock, flags);
> +
> + return ret;
> +}
> +
> +static void early_xdbc_write(struct console *con, const char *str, u32 n)
> +{
> + int chunk, ret;
> + static char buf[XDBC_MAX_PACKET];
> + int use_cr = 0;
> +
> + if (!xdbc.xdbc_reg)
> + return;
> + memset(buf, 0, XDBC_MAX_PACKET);
> + while (n > 0) {
> + for (chunk = 0; chunk < XDBC_MAX_PACKET && n > 0;
> + str++, chunk++, n--) {
> + if (!use_cr && *str == '\n') {
> + use_cr = 1;
> + buf[chunk] = '\r';
> + str--;
> + n++;
> + continue;
> + }
> + if (use_cr)
> + use_cr = 0;
> + buf[chunk] = *str;
> + }
> + if (chunk > 0) {
> + ret = xdbc_bulk_write(buf, chunk);
> + if (ret < 0)
> + break;
> + }
> + }
> +}
> +
> +static struct console early_xdbc_console = {
> + .name = "earlyxdbc",
> + .write = early_xdbc_write,
> + .flags = CON_PRINTBUFFER,
> + .index = -1,
> +};
> +
> +void __init early_xdbc_register_console(void)
> +{
> + if (early_console)
> + return;
> +
> + early_console = &early_xdbc_console;
> + if (early_console_keep)
> + early_console->flags &= ~CON_BOOT;
> + else
> + early_console->flags |= CON_BOOT;
> + register_console(early_console);
> +}
> +
> +static void xdbc_scrub_function(struct work_struct *work)
> +{
> + unsigned long flags;
> +
> + spin_lock_irqsave(&xdbc.lock, flags);
> +
> + /*
> + * DbC is running, check the event ring and
> + * handle the events.
> + */
> + if (readl(&xdbc.xdbc_reg->control) & CTRL_DRC)
> + xdbc_handle_events();
> +
> + /*
> + * External reset happened. Need to restart the
> + * debugging hardware.
> + */
> + if (unlikely(!(readl(&xdbc.xdbc_reg->control) & CTRL_DCE)))
> + xdbc_handle_external_reset();
> +
> + spin_unlock_irqrestore(&xdbc.lock, flags);
> +
> + queue_delayed_work(xdbc_wq, &xdbc.scrub, usecs_to_jiffies(100));
> +}
Excuse my total lack of USB knowledge, but WTH does this do and what do
we need it for?
next prev parent reply other threads:[~2016-10-19 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 0:18 [RESEND PATCH v2 0/4] usb: early: add support for early printk through USB3 debug port Lu Baolu
2016-10-19 0:18 ` [RESEND PATCH v2 1/4] usb: dbc: early driver for xhci debug capability Lu Baolu
2016-10-19 13:09 ` Peter Zijlstra [this message]
2016-10-20 8:08 ` Lu Baolu
2016-10-20 8:41 ` Peter Zijlstra
2016-10-20 9:08 ` Peter Zijlstra
2016-10-21 0:35 ` Lu Baolu
2016-10-19 0:18 ` [RESEND PATCH v2 2/4] x86: add support for earlyprintk via USB3 debug port Lu Baolu
2016-10-19 0:18 ` [RESEND PATCH v2 3/4] usb: serial: usb_debug: add support for dbc debug device Lu Baolu
2016-10-19 0:18 ` [RESEND PATCH v2 4/4] usb: doc: add document for USB3 debug port usage Lu Baolu
2016-10-19 7:48 ` Jani Nikula
2016-10-20 5:45 ` Lu Baolu
2016-10-20 8:30 ` Jani Nikula
2016-10-21 0:39 ` 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=20161019130943.GA3175@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=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.