From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Abhilash Jindal <klock.android@gmail.com>,
xen-devel@lists.xenproject.org
Cc: david.vrabel@citrix.com
Subject: Re: xen/pcifront: Use monotonic clock
Date: Sat, 08 Aug 2015 22:16:47 -0400 [thread overview]
Message-ID: <55C6B80F.7070704@oracle.com> (raw)
In-Reply-To: <CALiE4M1bWW-dqVBoK_YMAbg31LTk7xtrFrh=raBzPL8HChUu_A@mail.gmail.com>
On 08/08/2015 09:36 PM, Abhilash Jindal wrote:
> Wall time obtained from do_gettimeofday is susceptible to sudden jumps
> due to user setting the time or due to NTP.
>
> Monotonic time is constantly increasing time better suited for
> comparing two
> timestamps.
See commit e1d5bbcdc7ca08d8731f5d780f0de342a768d96a (you probably will
need to update your tree)
-boris
> ---
> drivers/pci/xen-pcifront.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/pci/xen-pcifront.c b/drivers/pci/xen-pcifront.c
> index f7197a7..5ef3eb7 100644
> --- a/drivers/pci/xen-pcifront.c
> +++ b/drivers/pci/xen-pcifront.c
> @@ -114,7 +114,7 @@ static int do_pci_op(struct pcifront_device *pdev,
> struct xen_pci_op *op)
> evtchn_port_t port = pdev->evtchn;
> unsigned irq = pdev->irq;
> s64 ns, ns_timeout;
> -struct timeval tv;
> +struct timespec tv;
> spin_lock_irqsave(&pdev->sh_info_lock, irq_flags);
> @@ -131,8 +131,8 @@ static int do_pci_op(struct pcifront_device *pdev,
> struct xen_pci_op *op)
> * (in the latter case we end up continually re-executing poll() with a
> * timeout in the past). 1s difference gives plenty of slack for error.
> */
> -do_gettimeofday(&tv);
> -ns_timeout = timeval_to_ns(&tv) + 2 * (s64)NSEC_PER_SEC;
> +ktime_get_ts(&tv);
> +ns_timeout = timespec_to_ns(&tv) + 2 * (s64)NSEC_PER_SEC;
> xen_clear_irq_pending(irq);
> @@ -140,8 +140,8 @@ static int do_pci_op(struct pcifront_device *pdev,
> struct xen_pci_op *op)
> (unsigned long *)&pdev->sh_info->flags)) {
> xen_poll_irq_timeout(irq, jiffies + 3*HZ);
> xen_clear_irq_pending(irq);
> -do_gettimeofday(&tv);
> -ns = timeval_to_ns(&tv);
> +ktime_get_ts(&tv);
> +ns = timespec_to_ns(&tv);
> if (ns > ns_timeout) {
> dev_err(&pdev->xdev->dev,
> "pciback not responding!!!\n");
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2015-08-09 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 1:36 xen/pcifront: Use monotonic clock Abhilash Jindal
2015-08-09 2:16 ` Boris Ostrovsky [this message]
2015-08-12 13:33 ` Abhilash Jindal
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=55C6B80F.7070704@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=klock.android@gmail.com \
--cc=xen-devel@lists.xenproject.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.