This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [SVM][PATCH] remove redundant do_softirq

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [SVM][PATCH] remove redundant do_softirq
From: "Woller, Thomas" <thomas.woller@xxxxxxx>
Date: Thu, 31 Aug 2006 17:16:03 -0500
Delivery-date: Thu, 31 Aug 2006 15:16:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbNSwvHkGSU9QVES9us3NPZbFdIkw==
Thread-topic: [SVM][PATCH] remove redundant do_softirq
> from Keir:
> Another thing: the code you have under case VMEXIT_INTR, which raises 
> schedule softirq, seems pointless. All interrupt work will happen in 
> proper interrupt context triggered on STGI. Should the code under 
> VMEXIT_INTR simply be removed?

Remove redundant do_softirq in the VMEXIT_INTR handler.

Applies cleanly to 11390.
Please apply to xen-unstable.hg.

Signed-off-by: Tom Woller <thomas.woller@xxxxxxx>

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>