From: Peter Maydell <peter.maydell@linaro.org>
To: P J P <ppandit@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Li Qiang <liqiang6-s@360.cn>, qemu-arm <qemu-arm@nongnu.org>,
Prasad J Pandit <pjp@fedoraproject.org>
Subject: Re: [Qemu-devel] [PATCH v6] timer: a9gtimer: remove loop to auto-increment comparator
Date: Mon, 17 Oct 2016 18:41:47 +0100 [thread overview]
Message-ID: <CAFEAcA8ALpL_rdgPL7dQbhx6prVV+ipXSoQ7LGu4ue_ReL9O-A@mail.gmail.com> (raw)
In-Reply-To: <1476416631-2870-1-git-send-email-ppandit@redhat.com>
On 14 October 2016 at 04:43, P J P <ppandit@redhat.com> wrote:
> From: Prasad J Pandit <pjp@fedoraproject.org>
>
> ARM A9MP processor has a peripheral timer with an auto-increment
> register, which holds an increment step value. A user could set
> this value to zero. When auto-increment control bit is enabled,
> it leads to an infinite loop in 'a9_gtimer_update' while
> updating comparator value. Remove this loop incrementing the
> comparator value.
>
> Reported-by: Li Qiang <liqiang6-s@360.cn>
> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
> ---
> hw/timer/a9gtimer.c | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> Update per
> -> https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg02891.html
>
> diff --git a/hw/timer/a9gtimer.c b/hw/timer/a9gtimer.c
> index 772f85f..03dfaf2 100644
> --- a/hw/timer/a9gtimer.c
> +++ b/hw/timer/a9gtimer.c
> @@ -73,6 +73,7 @@ static void a9_gtimer_update(A9GTimerState *s, bool sync)
>
> A9GTimerUpdate update = a9_gtimer_get_update(s);
> int i;
> + uint64_t inc;
> int64_t next_cdiff = 0;
>
> for (i = 0; i < s->num_cpu; ++i) {
> @@ -82,15 +83,15 @@ static void a9_gtimer_update(A9GTimerState *s, bool sync)
> if ((s->control & R_CONTROL_TIMER_ENABLE) &&
> (gtb->control & R_CONTROL_COMP_ENABLE)) {
> /* R2p0+, where the compare function is >= */
> - while (gtb->compare < update.new) {
> + if (gtb->compare < update.new) {
> DB_PRINT("Compare event happened for CPU %d\n", i);
> gtb->status = 1;
> - if (gtb->control & R_CONTROL_AUTO_INCREMENT) {
> - DB_PRINT("Auto incrementing timer compare by %" PRId32 "\n",
> - gtb->inc);
> - gtb->compare += gtb->inc;
> - } else {
> - break;
> + if (gtb->control & R_CONTROL_AUTO_INCREMENT && gtb->inc) {
> + inc = update.new + gtb->inc - gtb->compare - 1;
> + inc = QEMU_ALIGN_DOWN(inc, gtb->inc);
Isn't this pair of lines equivalent to
uint64_t inc = QEMU_ALIGN_UP(update.new - gtb->compare, gtb->inc);
?
I think using that macro makes it clearer that the code is correct.
If you replace the above two lines (and the unnecessarily widely
scoped declaration of inc) with that line then you can have
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> + DB_PRINT("Auto incrementing timer compare by %"
> + PRId64 "\n", inc);
> + gtb->compare += inc;
> }
> }
> cdiff = (int64_t)gtb->compare - (int64_t)update.new + 1;
> --
> 2.5.5
thanks
-- PMM
next prev parent reply other threads:[~2016-10-17 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 3:43 [Qemu-devel] [PATCH v6] timer: a9gtimer: remove loop to auto-increment comparator P J P
2016-10-17 17:41 ` Peter Maydell [this message]
2016-10-17 18:41 ` P J P
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=CAFEAcA8ALpL_rdgPL7dQbhx6prVV+ipXSoQ7LGu4ue_ReL9O-A@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=liqiang6-s@360.cn \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).