All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: freebsd-xen@freebsd.org
Cc: xen-devel@lists.xenproject.org, sstabellini@kernel.org,
	roger.pau@citrix.com
Subject: [PATCH] xen/x86: don't lose event interrupts
Date: Thu, 21 Apr 2016 14:34:25 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1604211432440.23110@sstabellini-ThinkPad-X260> (raw)

xen/x86: don't lose event interrupts

On slow platforms with unreliable TSC, such as QEMU emulated machines,
it is possible for the FreeBSD kernel to request the next event in the
past. In that case, in the current implementation of
xentimer_vcpu_start_timer, we simply return -ETIME. To be precise Xen
returns -ETIME and we pass it on. As a consequence we need to loop
around to function to make sure that the timer is properly set.

Instead it is better to always ask the hypervisor for a timer event,
even if the timeout is past. To do that, remove the VCPU_SSHOTTMR_future
flag.

Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>

diff --git a/sys/dev/xen/timer/timer.c b/sys/dev/xen/timer/timer.c
index 53aff0a..db9b19b 100644
--- a/sys/dev/xen/timer/timer.c
+++ b/sys/dev/xen/timer/timer.c
@@ -267,7 +267,8 @@ xentimer_vcpu_start_timer(int vcpu, uint64_t next_time)
 	struct vcpu_set_singleshot_timer single;
 
 	single.timeout_abs_ns = next_time;
-	single.flags          = VCPU_SSHOTTMR_future;
+	/* Get an event anyway, even if the timeout is already expired */
+	single.flags          = 0;
 	return (HYPERVISOR_vcpu_op(VCPUOP_set_singleshot_timer, vcpu, &single));
 }
 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2016-04-21 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 13:34 Stefano Stabellini [this message]
2016-05-02 18:09 ` [PATCH] xen/x86: don't lose event interrupts Roger Pau Monné
  -- strict thread matches above, loose matches on Subject: below --
2016-04-16  1:23 Stefano Stabellini
2016-04-16  1:23 Stefano Stabellini
2016-04-21  8:59 ` Juergen Gross
2016-04-21  8:59 ` Juergen Gross
2016-04-25 10:28   ` Stefano Stabellini
2016-04-25 10:28   ` Stefano Stabellini

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=alpine.DEB.2.10.1604211432440.23110@sstabellini-ThinkPad-X260 \
    --to=sstabellini@kernel.org \
    --cc=freebsd-xen@freebsd.org \
    --cc=roger.pau@citrix.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.