[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAC5umygcfno0-=rA9G0OcxuVK2YK9UokfoYoy45qBT8w0+ytvg@mail.gmail.com>
Date: Wed, 27 Jul 2011 08:17:18 +0900
From: Akinobu Mita <akinobu.mita@...il.com>
To: Per Forlin <per.forlin@...aro.org>
Cc: linaro-dev@...ts.linaro.org,
Nicolas Pitre <nicolas.pitre@...aro.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mmc@...r.kernel.org, linux-doc@...r.kernel.org,
Venkatraman S <svenkatr@...com>,
Linus Walleij <linus.walleij@...aro.org>,
Kyungmin Park <kyungmin.park@...sung.com>,
Arnd Bergmann <arnd@...db.de>,
Sourav Poddar <sourav.poddar@...com>,
Chris Ball <cjb@...top.org>,
J Freyensee <james_p_freyensee@...ux.intel.com>,
Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [PATCH v4 2/3] mmc: core: add random fault injection
2011/7/27 Per Forlin <per.forlin@...aro.org>:
> This adds support to inject data errors after a completed host transfer.
> The mmc core will return error even though the host transfer is successful.
> This simple fault injection proved to be very useful to test the
> non-blocking error handling in the mmc_blk_issue_rw_rq().
> Random faults can also test how the host driver handles pre_req()
> and post_req() in case of errors.
Looks good but I have one question.
> @@ -304,6 +307,10 @@ struct mmc_host {
>
> struct mmc_async_req *areq; /* active async req */
>
> +#ifdef CONFIG_FAIL_MMC_REQUEST
> + u8 make_it_fail;
> + struct fault_attr fail_mmc_request;
> +#endif
> unsigned long private[0] ____cacheline_aligned;
> };
I think make_it_fail is not needed anymore because if fail_attr is
defined per-host then you can enable it by setting probability=0
or times=0 per-host.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists