[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH] xen: privcmd: schedule() after private hypercall when non CONFIG_PREEMPT
- To: "Luis R. Rodriguez" <mcgrof@xxxxxxxx>, David Vrabel <david.vrabel@xxxxxxxxxx>
- From: David Vrabel <david.vrabel@xxxxxxxxxx>
- Date: Tue, 2 Dec 2014 11:11:18 +0000
- Cc: Juergen Gross <jgross@xxxxxxxx>, Joerg Roedel <jroedel@xxxxxxx>, kvm@xxxxxxxxxxxxxxx, Davidlohr Bueso <dbueso@xxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, x86@xxxxxxxxxx, Oleg Nesterov <oleg@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, boris.ostrovsky@xxxxxxxxxx, Borislav Petkov <bp@xxxxxxx>, Olaf Hering <ohering@xxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>
- Delivery-date: Tue, 02 Dec 2014 11:11:47 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 01/12/14 22:36, Luis R. Rodriguez wrote:
>
> Then I do agree its a fair analogy (and find this obviously odd that how
> widespread cond_resched() is), we just don't have an equivalent for IRQ
> context, why not avoid the special check then and use this all the time in the
> middle of a hypercall on the return from an interrupt (e.g., the timer
> interrupt)?
http://lists.xen.org/archives/html/xen-devel/2014-02/msg01101.html
David
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
