All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
Cc: qemu-devel@nongnu.org, mst@redhat.com, dgilbert@redhat.com,
	maria.klimushenkova@ispras.ru, dovgaluk@ispras.ru,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] hpet: recover timer offset correctly
Date: Wed, 10 Jan 2018 11:47:13 +0100	[thread overview]
Message-ID: <874lnuyor2.fsf@secure.laptop> (raw)
In-Reply-To: <20180110100929.15986.71777.stgit@pasha-VirtualBox> (Pavel Dovgalyuk's message of "Wed, 10 Jan 2018 13:09:30 +0300")

Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru> wrote:
> HPET saves its state by calculating the current time and recovers timer
> offset using this calculated value. But these calculations include
> divisions and multiplications. Therefore the timer state cannot be recovered
> precise enough.
> This patch introduces saving of the original value of the offset to
> preserve the determinism of the timer.
>
> Signed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
> Signed-off-by: Maria Klimushenkova <maria.klimushenkova@ispras.ru>
> Reviewed-by: Juan Quintela <quintela@redhat.com>
>
> --
> v3: Added compat property for correct migration.

Yeap, Much better.

> @@ -762,6 +787,7 @@ static Property hpet_device_properties[] = {
>      DEFINE_PROP_UINT8("timers", HPETState, num_timers, HPET_MIN_TIMERS),
>      DEFINE_PROP_BIT("msi", HPETState, flags, HPET_MSI_SUPPORT, false),
>      DEFINE_PROP_UINT32(HPET_INTCAP, HPETState, intcap, 0),
> +    DEFINE_PROP_BOOL("hpet-offset-saved", HPETState, hpet_offset_saved, true),
>      DEFINE_PROP_END_OF_LIST(),
>  };

I am thinking about the name, but I can't suggest anything else that is
short and descriptive, so ....

Later, Juan.

      reply	other threads:[~2018-01-10 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 10:09 [Qemu-devel] [PATCH v3] hpet: recover timer offset correctly Pavel Dovgalyuk
2018-01-10 10:47 ` Juan Quintela [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=874lnuyor2.fsf@secure.laptop \
    --to=quintela@redhat.com \
    --cc=Pavel.Dovgaluk@ispras.ru \
    --cc=dgilbert@redhat.com \
    --cc=dovgaluk@ispras.ru \
    --cc=maria.klimushenkova@ispras.ru \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --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 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.