From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/9] genirq/timings: Fix next event index function
Date: Fri, 24 May 2019 16:51:45 +0300 [thread overview]
Message-ID: <20190524135145.GW9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190524111615.4891-2-daniel.lezcano@linaro.org>
On Fri, May 24, 2019 at 01:16:07PM +0200, Daniel Lezcano wrote:
> The current code was luckily working with most of the interval samples
> testing but actually it fails to correctly detect pattern repeatition
> breaking at the end of the buffer.
>
> Narrowing down the bug has been a real pain because of the pointers,
> so the routine is rewrite by using indexes instead.
Minor spelling issues below.
> + /*
> + * Move the beginnning pointer to the end minus the max period
Typo: beginning.
> + * x 3. We are at the point we can begin searching the pattern
"x 3." would be read better on the previous line.
> + */
> + buffer = &buffer[len - (period_max * 3)];
> + /*
> + * Adjust the length to the maximum allowed period x 3
> + */
One line?
> + len = period_max * 3;
> - for (i = period_max; i >= PREDICTION_PERIOD_MIN ; i--) {
> + for (period = period_max; period >= PREDICTION_PERIOD_MIN ; period--) {
At the same time you may drop extra white space.
> }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-05-24 13:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 11:16 [PATCH V2 0/9] genirq/timings: Fixes and selftests Daniel Lezcano
2019-05-24 11:16 ` [PATCH V2 1/9] genirq/timings: Fix next event index function Daniel Lezcano
2019-05-24 13:51 ` Andy Shevchenko [this message]
2019-05-24 11:16 ` [PATCH V2 2/9] genirq/timings: Fix timings buffer inspection Daniel Lezcano
2019-05-24 11:16 ` [PATCH V2 3/9] genirq/timings: Optimize the period detection speed Daniel Lezcano
2019-05-24 11:16 ` [PATCH V2 4/9] genirq/timings: Use the min kernel macro Daniel Lezcano
2019-05-24 13:57 ` Andy Shevchenko
2019-05-24 16:11 ` Daniel Lezcano
2019-05-24 11:16 ` [PATCH V2 5/9] genirq/timings: Encapsulate timings push Daniel Lezcano
2019-05-24 11:16 ` [PATCH V2 6/9] genirq/timings: Encapsulate storing function Daniel Lezcano
2019-05-24 11:16 ` [PATCH V2 7/9] genirq/timings: Add selftest for circular array Daniel Lezcano
2019-05-24 14:00 ` Andy Shevchenko
2019-05-24 16:00 ` Daniel Lezcano
2019-05-24 11:16 ` [PATCH V2 8/9] genirq/timings: Add selftest for irqs circular buffer Daniel Lezcano
2019-05-24 11:16 ` [PATCH V2 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=20190524135145.GW9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).