From: per.forlin@linaro.org (Per Forlin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] fault injection: add documentation on MMC IO fault injection
Date: Thu, 21 Jul 2011 00:02:01 +0200 [thread overview]
Message-ID: <1311199321-4618-4-git-send-email-per.forlin@linaro.org> (raw)
In-Reply-To: <1311199321-4618-1-git-send-email-per.forlin@linaro.org>
Add description on how to enable random fault injection
for MMC IO
Signed-off-by: Per Forlin <per.forlin@linaro.org>
---
Documentation/fault-injection/fault-injection.txt | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/Documentation/fault-injection/fault-injection.txt b/Documentation/fault-injection/fault-injection.txt
index 7be15e4..27eede4 100644
--- a/Documentation/fault-injection/fault-injection.txt
+++ b/Documentation/fault-injection/fault-injection.txt
@@ -21,6 +21,11 @@ o fail_make_request
/sys/block/<device>/make-it-fail or
/sys/block/<device>/<partition>/make-it-fail. (generic_make_request())
+o fail_mmc_request
+
+ injects MMC data errors on devices permitted by setting
+ /sys/kernel/debug/mmc0/make-it-fail
+
Configure fault-injection capabilities behavior
-----------------------------------------------
--
1.7.4.1
prev parent reply other threads:[~2011-07-20 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 22:01 [PATCH v3 0/3] Make fault injection available for MMC IO Per Forlin
2011-07-20 22:01 ` [PATCH v3 1/3] fault-inject: make fault injection available for modules Per Forlin
2011-07-20 22:02 ` [PATCH v3 2/3] mmc: core: add random fault injection Per Forlin
2011-07-25 15:58 ` Akinobu Mita
2011-07-25 19:19 ` Per Forlin
2011-07-25 21:20 ` Per Forlin
2011-07-26 1:41 ` Akinobu Mita
2011-07-26 20:01 ` Per Forlin
2011-07-26 20:08 ` Per Forlin
2011-07-20 22:02 ` Per Forlin [this message]
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=1311199321-4618-4-git-send-email-per.forlin@linaro.org \
--to=per.forlin@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).