public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: usbmon, usb core, ARM
Date: Sat, 22 Jan 2005 00:12:37 -0800	[thread overview]
Message-ID: <20050122001237.38596a5b@localhost.localdomain> (raw)
In-Reply-To: <200501202228.31840.david-b@pacbell.net>

On Thu, 20 Jan 2005 22:28:31 -0800, David Brownell <david-b@pacbell.net> wrote:

> By the way ... on the topic of usbmon rather than changing
> usbcore, is there a brief writeup of what you want this
> new version to be doing -- and how?  Like, why put the
> spy hooks in that location, rather than any of the other
> choices.  (Many of them would be less surprising to me!)

The main idea was to make usbmon invisible if it's not actively monitoring.
But after thinking about your message I see that it was a misguided approach.
I'm going to add "if (usbmon_is_running(bus)) usb_mon_hook(bus, urb);" into
hot paths instead, approximately where current suggestion comments are.

I cannot figure out if you understand the nature of the problem with current
usbmon, so let me restate it. Simply put, neither dev nor hcd are available
at the time urb->complete is called, and this is what usbmon intercepts.
For one thing, dev is down-counted in usb_unlink_urb(). This is why I tried
to find a way to avoid using them. Your "dev == hcd->self.root_hub" is
entirely out of question. But it's probably a moot point now anyway.

Adding hooks explicitly has its disadvantages. Although the giveback
path is much better, in the submit path such hook cannot inform usbmon
if the submission fails, and an additional hook is needed. Anyhow, you'll
see it all in the patch, please give me a couple of days.

Greetings,
-- Pete

  reply	other threads:[~2005-01-22  8:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19  5:20 usbmon, usb core, ARM Pete Zaitcev
2005-01-19  6:14 ` David Brownell
2005-01-19 15:42   ` Pete Zaitcev
2005-01-19 15:54     ` Oliver Neukum
2005-01-19 17:08     ` David Brownell
2005-01-20 19:35       ` Pete Zaitcev
2005-01-21  6:28         ` David Brownell
2005-01-22  8:12           ` Pete Zaitcev [this message]
2005-01-23 23:34             ` [linux-usb-devel] " David Brownell
2005-01-24  1:17               ` Pete Zaitcev
2005-01-24  2:08                 ` David Brownell

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=20050122001237.38596a5b@localhost.localdomain \
    --to=zaitcev@redhat.com \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox