From: Michael Buesch <mb@bu3sch.de>
To: linux-wireless@vger.kernel.org
Cc: Jiri Benc <jbenc@suse.cz>, Michael Wu <flamingice@sourmilk.net>
Subject: bcm43xx: New feature: Injection of TX queue overflows
Date: Sat, 2 Jun 2007 23:21:43 +0200 [thread overview]
Message-ID: <200706022321.43198.mb@bu3sch.de> (raw)
I added a feature to my tree that makes it possible to
conveniently inject a simulated TX queue overflow every
second. This could be used to test code in the stack
that's handling this rare event that almost never happens
in the real world (with sane hardware, at least :) )
http://bu3sch.de/gitweb?p=wireless-dev.git;a=commitdiff;h=3dd01baded24ff2d35bb0e5dac5dd2d90932f926
You need to compile bcm43xx-mac80211 with debugging support.
The injection is enabled at runtime through debugfs
by doing:
echo 1 >/debug/bcm43xx_mac80211/phyX/debug_dmaoverflow
It prints a debugging message to dmesg every time it
injects a fault.
--
Greetings Michael.
reply other threads:[~2007-06-02 21:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200706022321.43198.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=linux-wireless@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).