* [PATCH] xen/x86: don't lose event interrupts
@ 2016-04-21 13:34 Stefano Stabellini
2016-05-02 18:09 ` Roger Pau Monné
0 siblings, 1 reply; 5+ messages in thread
From: Stefano Stabellini @ 2016-04-21 13:34 UTC (permalink / raw)
To: freebsd-xen; +Cc: xen-devel, sstabellini, roger.pau
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
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH] xen/x86: don't lose event interrupts
2016-04-21 13:34 [PATCH] xen/x86: don't lose event interrupts Stefano Stabellini
@ 2016-05-02 18:09 ` Roger Pau Monné
0 siblings, 0 replies; 5+ messages in thread
From: Roger Pau Monné @ 2016-05-02 18:09 UTC (permalink / raw)
To: Stefano Stabellini; +Cc: freebsd-xen, xen-devel
On Thu, Apr 21, 2016 at 02:34:25PM +0100, Stefano Stabellini wrote:
> 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>
Thanks, it's now committed:
https://svnweb.freebsd.org/base?view=revision&revision=298926
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <alpine.DEB.2.10.1604151814580.2526@sstabellini-ThinkPad-X260>]
* Re: [PATCH] xen/x86: don't lose event interrupts
[not found] <alpine.DEB.2.10.1604151814580.2526@sstabellini-ThinkPad-X260>
@ 2016-04-21 8:59 ` Juergen Gross
[not found] ` <57189659.6040807@suse.com>
1 sibling, 0 replies; 5+ messages in thread
From: Juergen Gross @ 2016-04-21 8:59 UTC (permalink / raw)
To: Stefano Stabellini, xen-devel; +Cc: boris.ostrovsky, linux-kernel, david.vrabel
On 16/04/16 03:23, Stefano Stabellini wrote:
> On slow platforms with unreliable TSC, such as QEMU emulated machines,
> it is possible for the kernel to request the next event in the past. In
> that case, in the current implementation of xen_vcpuop_clockevent, we
> simply return -ETIME. To be precise the Xen returns -ETIME and we pass
> it on. However the result of this is a missed event, which simply causes
> the kernel to hang.
>
> Instead it is better to always ask the hypervisor for a timer event,
> even if the timeout is in the past. That way there are no lost
> interrupts and the kernel survives. To do that, remove the
> VCPU_SSHOTTMR_future flag.
>
> Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
Acked-by: Juergen Gross <jgross@suse.com>
>
> diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
> index a0a4e55..6deba5b 100644
> --- a/arch/x86/xen/time.c
> +++ b/arch/x86/xen/time.c
> @@ -290,11 +290,11 @@ static int xen_vcpuop_set_next_event(unsigned long delta,
> WARN_ON(!clockevent_state_oneshot(evt));
>
> single.timeout_abs_ns = get_abs_timeout(delta);
> - single.flags = VCPU_SSHOTTMR_future;
> + /* Get an event anyway, even if the timeout is already expired */
> + single.flags = 0;
>
> ret = HYPERVISOR_vcpu_op(VCPUOP_set_singleshot_timer, cpu, &single);
> -
> - BUG_ON(ret != 0 && ret != -ETIME);
> + BUG_ON(ret != 0);
>
> return ret;
> }
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread[parent not found: <57189659.6040807@suse.com>]
* Re: [PATCH] xen/x86: don't lose event interrupts
[not found] ` <57189659.6040807@suse.com>
@ 2016-04-25 10:28 ` Stefano Stabellini
0 siblings, 0 replies; 5+ messages in thread
From: Stefano Stabellini @ 2016-04-25 10:28 UTC (permalink / raw)
To: Juergen Gross
Cc: xen-devel, boris.ostrovsky, Stefano Stabellini, linux-kernel,
david.vrabel
On Thu, 21 Apr 2016, Juergen Gross wrote:
> On 16/04/16 03:23, Stefano Stabellini wrote:
> > On slow platforms with unreliable TSC, such as QEMU emulated machines,
> > it is possible for the kernel to request the next event in the past. In
> > that case, in the current implementation of xen_vcpuop_clockevent, we
> > simply return -ETIME. To be precise the Xen returns -ETIME and we pass
> > it on. However the result of this is a missed event, which simply causes
> > the kernel to hang.
> >
> > Instead it is better to always ask the hypervisor for a timer event,
> > even if the timeout is in the past. That way there are no lost
> > interrupts and the kernel survives. To do that, remove the
> > VCPU_SSHOTTMR_future flag.
> >
> > Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
>
> Acked-by: Juergen Gross <jgross@suse.com>
I committed it to xentip/for-linus-4.7
> > diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
> > index a0a4e55..6deba5b 100644
> > --- a/arch/x86/xen/time.c
> > +++ b/arch/x86/xen/time.c
> > @@ -290,11 +290,11 @@ static int xen_vcpuop_set_next_event(unsigned long delta,
> > WARN_ON(!clockevent_state_oneshot(evt));
> >
> > single.timeout_abs_ns = get_abs_timeout(delta);
> > - single.flags = VCPU_SSHOTTMR_future;
> > + /* Get an event anyway, even if the timeout is already expired */
> > + single.flags = 0;
> >
> > ret = HYPERVISOR_vcpu_op(VCPUOP_set_singleshot_timer, cpu, &single);
> > -
> > - BUG_ON(ret != 0 && ret != -ETIME);
> > + BUG_ON(ret != 0);
> >
> > return ret;
> > }
> >
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH] xen/x86: don't lose event interrupts
@ 2016-04-16 1:23 Stefano Stabellini
0 siblings, 0 replies; 5+ messages in thread
From: Stefano Stabellini @ 2016-04-16 1:23 UTC (permalink / raw)
To: xen-devel
Cc: jgross, boris.ostrovsky, sstabellini, linux-kernel, david.vrabel
On slow platforms with unreliable TSC, such as QEMU emulated machines,
it is possible for the kernel to request the next event in the past. In
that case, in the current implementation of xen_vcpuop_clockevent, we
simply return -ETIME. To be precise the Xen returns -ETIME and we pass
it on. However the result of this is a missed event, which simply causes
the kernel to hang.
Instead it is better to always ask the hypervisor for a timer event,
even if the timeout is in the past. That way there are no lost
interrupts and the kernel survives. To do that, remove the
VCPU_SSHOTTMR_future flag.
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
index a0a4e55..6deba5b 100644
--- a/arch/x86/xen/time.c
+++ b/arch/x86/xen/time.c
@@ -290,11 +290,11 @@ static int xen_vcpuop_set_next_event(unsigned long delta,
WARN_ON(!clockevent_state_oneshot(evt));
single.timeout_abs_ns = get_abs_timeout(delta);
- single.flags = VCPU_SSHOTTMR_future;
+ /* Get an event anyway, even if the timeout is already expired */
+ single.flags = 0;
ret = HYPERVISOR_vcpu_op(VCPUOP_set_singleshot_timer, cpu, &single);
-
- BUG_ON(ret != 0 && ret != -ETIME);
+ BUG_ON(ret != 0);
return ret;
}
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply related [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-05-02 18:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-21 13:34 [PATCH] xen/x86: don't lose event interrupts Stefano Stabellini
2016-05-02 18:09 ` Roger Pau Monné
[not found] <alpine.DEB.2.10.1604151814580.2526@sstabellini-ThinkPad-X260>
2016-04-21 8:59 ` Juergen Gross
[not found] ` <57189659.6040807@suse.com>
2016-04-25 10:28 ` Stefano Stabellini
-- strict thread matches above, loose matches on Subject: below --
2016-04-16 1:23 Stefano Stabellini
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).