From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Kees Cook <keescook@chromium.org>, Petr Mladek <pmladek@suse.com>,
Matthew Wilcox <willy@infradead.org>,
Joe Lawrence <joe.lawrence@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Robin Murphy <robin.murphy@arm.com>,
Sri Krishna chowdary <schowdary@nvidia.com>,
Changbin Du <changbin.du@intel.com>
Subject: Re: [PATCH 7/9] genirq/timings: Add selftest for circular array
Date: Mon, 13 May 2019 13:50:27 +0300 [thread overview]
Message-ID: <20190513105027.GQ9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190513102953.16424-8-daniel.lezcano@linaro.org>
On Mon, May 13, 2019 at 12:29:51PM +0200, Daniel Lezcano wrote:
> Due to the complexity of the code and the difficulty to debug it,
> let's add some selftests to the framework in order to spot issues or
> regression at boot time when the runtime testing is enabled for this
> subsystem.
>
> This tests the circular buffer at the limits and validates:
> - the encoding / decoding of the values
> - the macro to browse the irq timings circular buffer
> - the function to push data in the circular buffer
> kernel/irq/timings.c | 119 +++++++++++++++++++++++++++++++++++++++++++
Is it possible to have it in a separate C-file?
> +config TEST_IRQ_TIMINGS
> + bool "IRQ timings selftest"
> + default n
This is already default.
> + depends on IRQ_TIMINGS
> + help
> + Enable this option to test the irq timings code on boot.
> +
> + If unsure, say N.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-05-13 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 10:29 [PATCH 0/9] genirq/timings: Fixes and selftests Daniel Lezcano
2019-05-13 10:29 ` [PATCH 1/9] genirq/timings: Fix next event index function Daniel Lezcano
2019-05-13 10:29 ` [PATCH 2/9] genirq/timings: Fix timings buffer inspection Daniel Lezcano
2019-05-13 10:29 ` [PATCH 3/9] genirq/timings: Optimize the period detection speed Daniel Lezcano
2019-05-13 10:29 ` [PATCH 4/9] genirq/timings: Use the min kernel macro Daniel Lezcano
2019-05-13 10:29 ` [PATCH 5/9] genirq/timings: Encapsulate timings push Daniel Lezcano
2019-05-13 10:29 ` [PATCH 6/9] genirq/timings: Encapsulate storing function Daniel Lezcano
2019-05-13 10:29 ` [PATCH 7/9] genirq/timings: Add selftest for circular array Daniel Lezcano
2019-05-13 10:50 ` Andy Shevchenko [this message]
2019-05-13 11:03 ` Daniel Lezcano
2019-05-13 10:29 ` [PATCH 8/9] genirq/timings: Add selftest for irqs circular buffer Daniel Lezcano
2019-05-13 10:29 ` [PATCH 9/9] genirq/timings: Add selftest for next event computation Daniel Lezcano
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=20190513105027.GQ9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=changbin.du@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=joe.lawrence@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--cc=robin.murphy@arm.com \
--cc=schowdary@nvidia.com \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=yamada.masahiro@socionext.com \
/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
all inboxes | Powered by JetHome®