Hi Pete,
> > While I am really thinking about starting usbdump, I may ask why you
> > have choosen to use debugfs as interface. This will not be available in
> > normal distribution kernels and I think a general USB monitoring ability
> > would be great. For example like we have it for Ethernet,
On Tue, Feb 01, 2005 at 10:25:13PM -0800, Pete Zaitcev wrote:
> This patch adds so-called "usbmon", or USB monitoring framework, similar
> to what tcpdump provides for Ethernet. This is an initial version, but
> it should be safe and useful. It adds an overhead of an if () statement
> into
On Tue, Feb 01, 2005 at 10:25:13PM -0800, Pete Zaitcev wrote:
This patch adds so-called usbmon, or USB monitoring framework, similar
to what tcpdump provides for Ethernet. This is an initial version, but
it should be safe and useful. It adds an overhead of an if () statement
into submission
Hi Pete,
While I am really thinking about starting usbdump, I may ask why you
have choosen to use debugfs as interface. This will not be available in
normal distribution kernels and I think a general USB monitoring ability
would be great. For example like we have it for Ethernet,
On Wed, 02 Feb 2005 17:40:17 +0100, Marcel Holtmann <[EMAIL PROTECTED]> wrote:
> While I am really thinking about starting usbdump, I may ask why you
> have choosen to use debugfs as interface. This will not be available in
> normal distribution kernels and I think a general USB monitoring
Hi Pete,
> > I think if cat is the prefered tool for viewing this file then it should
> > be more human readable. If not, then a binary format should be choosen.
> > Maybe we can implement both. Is this possible?
>
> Yes. Now you know why files were split as they were.
still no reason for me to
Hi Pete,
I think if cat is the prefered tool for viewing this file then it should
be more human readable. If not, then a binary format should be choosen.
Maybe we can implement both. Is this possible?
Yes. Now you know why files were split as they were.
still no reason for me to split
On Wed, 02 Feb 2005 17:40:17 +0100, Marcel Holtmann [EMAIL PROTECTED] wrote:
While I am really thinking about starting usbdump, I may ask why you
have choosen to use debugfs as interface. This will not be available in
normal distribution kernels and I think a general USB monitoring ability
This patch adds so-called "usbmon", or USB monitoring framework, similar
to what tcpdump provides for Ethernet. This is an initial version, but
it should be safe and useful. It adds an overhead of an if () statement
into submission and giveback paths even when not monitoring, but this
was deemed a
On Tue, 01 Feb 2005 22:37:50 +0100, Marcel Holtmann <[EMAIL PROTECTED]> wrote:
> I think if cat is the prefered tool for viewing this file then it should
> be more human readable. If not, then a binary format should be choosen.
> Maybe we can implement both. Is this possible?
Yes. Now you know
Hi Pete,
> > By accident I removed the debugfs option from my kernel config and this
> > makes usbmon totally useless. So I think the module approach is wrong
> > from my point of view. Why not compile it always and if debugfs is
> > available, then enable it when the usbcore gets loaded?
>
>
On Tue, 01 Feb 2005 12:13:03 +0100, Marcel Holtmann <[EMAIL PROTECTED]> wrote:
> By accident I removed the debugfs option from my kernel config and this
> makes usbmon totally useless. So I think the module approach is wrong
> from my point of view. Why not compile it always and if debugfs is
>
Hi Pete,
today I just thought to give usbmon a try. Previously I used a hacked
devio thing around usbfs_snoop to monitor the USB communication between
a VMware and the Linux host.
Greg, will such patch accepted for inclusion or will usbfs_snoop go away
when usbmon is included?
> > First off,
On Mon, 31 Jan 2005 23:10:01 -0800, Greg KH <[EMAIL PROTECTED]> wrote:
> First off, why make usbmon a module? You aren't allowing it to happen,
> so just take out the parts of the patch that allow it.
No, I do allow it. This way I can load and unload it when debugging it.
Perhaps in the future
On Mon, 31 Jan 2005 23:10:01 -0800, Greg KH [EMAIL PROTECTED] wrote:
First off, why make usbmon a module? You aren't allowing it to happen,
so just take out the parts of the patch that allow it.
No, I do allow it. This way I can load and unload it when debugging it.
Perhaps in the future we
Hi Pete,
today I just thought to give usbmon a try. Previously I used a hacked
devio thing around usbfs_snoop to monitor the USB communication between
a VMware and the Linux host.
Greg, will such patch accepted for inclusion or will usbfs_snoop go away
when usbmon is included?
First off, why
On Tue, 01 Feb 2005 12:13:03 +0100, Marcel Holtmann [EMAIL PROTECTED] wrote:
By accident I removed the debugfs option from my kernel config and this
makes usbmon totally useless. So I think the module approach is wrong
from my point of view. Why not compile it always and if debugfs is
Hi Pete,
By accident I removed the debugfs option from my kernel config and this
makes usbmon totally useless. So I think the module approach is wrong
from my point of view. Why not compile it always and if debugfs is
available, then enable it when the usbcore gets loaded?
This may be
On Tue, 01 Feb 2005 22:37:50 +0100, Marcel Holtmann [EMAIL PROTECTED] wrote:
I think if cat is the prefered tool for viewing this file then it should
be more human readable. If not, then a binary format should be choosen.
Maybe we can implement both. Is this possible?
Yes. Now you know why
This patch adds so-called usbmon, or USB monitoring framework, similar
to what tcpdump provides for Ethernet. This is an initial version, but
it should be safe and useful. It adds an overhead of an if () statement
into submission and giveback paths even when not monitoring, but this
was deemed a
On Mon, Jan 31, 2005 at 09:29:03PM -0800, Pete Zaitcev wrote:
> This patch adds so-called "usbmon", or USB monitoring framework, similar
> to what tcpdump provides for Ethernet. This is an initial version, but
> it should be safe and useful. It adds an overhead of an if () statement
> into
This patch adds so-called "usbmon", or USB monitoring framework, similar
to what tcpdump provides for Ethernet. This is an initial version, but
it should be safe and useful. It adds an overhead of an if () statement
into submission and giveback paths even when not monitoring, but this
was deemed a
This patch adds so-called usbmon, or USB monitoring framework, similar
to what tcpdump provides for Ethernet. This is an initial version, but
it should be safe and useful. It adds an overhead of an if () statement
into submission and giveback paths even when not monitoring, but this
was deemed a
On Mon, Jan 31, 2005 at 09:29:03PM -0800, Pete Zaitcev wrote:
This patch adds so-called usbmon, or USB monitoring framework, similar
to what tcpdump provides for Ethernet. This is an initial version, but
it should be safe and useful. It adds an overhead of an if () statement
into submission
24 matches
Mail list logo
