All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <laurent@vivier.eu>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	Andrew Randrianasulu <randrianasulu@gmail.com>
Subject: Re: [PATCH] mos6522: update counters when timer interrupts are off
Date: Tue, 26 Nov 2019 10:12:17 +1100	[thread overview]
Message-ID: <20191125231217.GI5582@umbus.fritz.box> (raw)
In-Reply-To: <20191125141414.5015-1-laurent@vivier.eu>

[-- Attachment #1: Type: text/plain, Size: 2171 bytes --]

On Mon, Nov 25, 2019 at 03:14:14PM +0100, Laurent Vivier wrote:
> Even if the interrupts are off, counters must be updated because
> they are running anyway and kernel can try to read them
> (it's the case with g3beige kernel).
> 
> Reported-by: Andrew Randrianasulu <randrianasulu@gmail.com>
> Signed-off-by: Laurent Vivier <laurent@vivier.eu>

Applied to ppc-for-4.2, thanks.

> ---
>  hw/misc/mos6522.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/misc/mos6522.c b/hw/misc/mos6522.c
> index aa3bfe1afd..cecf0be59e 100644
> --- a/hw/misc/mos6522.c
> +++ b/hw/misc/mos6522.c
> @@ -113,6 +113,10 @@ static int64_t get_next_irq_time(MOS6522State *s, MOS6522Timer *ti,
>      int64_t d, next_time;
>      unsigned int counter;
>  
> +    if (ti->frequency == 0) {
> +        return INT64_MAX;
> +    }
> +
>      /* current counter value */
>      d = muldiv64(qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) - ti->load_time,
>                   ti->frequency, NANOSECONDS_PER_SECOND);
> @@ -149,10 +153,10 @@ static void mos6522_timer1_update(MOS6522State *s, MOS6522Timer *ti,
>      if (!ti->timer) {
>          return;
>      }
> +    ti->next_irq_time = get_next_irq_time(s, ti, current_time);
>      if ((s->ier & T1_INT) == 0 || (s->acr & T1MODE) != T1MODE_CONT) {
>          timer_del(ti->timer);
>      } else {
> -        ti->next_irq_time = get_next_irq_time(s, ti, current_time);
>          timer_mod(ti->timer, ti->next_irq_time);
>      }
>  }
> @@ -163,10 +167,10 @@ static void mos6522_timer2_update(MOS6522State *s, MOS6522Timer *ti,
>      if (!ti->timer) {
>          return;
>      }
> +    ti->next_irq_time = get_next_irq_time(s, ti, current_time);
>      if ((s->ier & T2_INT) == 0) {
>          timer_del(ti->timer);
>      } else {
> -        ti->next_irq_time = get_next_irq_time(s, ti, current_time);
>          timer_mod(ti->timer, ti->next_irq_time);
>      }
>  }

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2019-11-25 23:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 14:14 [PATCH] mos6522: update counters when timer interrupts are off Laurent Vivier
2019-11-25 14:37 ` Philippe Mathieu-Daudé
2019-11-25 14:56   ` Laurent Vivier
2019-11-25 15:00     ` Philippe Mathieu-Daudé
2019-11-25 23:12 ` David Gibson [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=20191125231217.GI5582@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=laurent@vivier.eu \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=randrianasulu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.