WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] do_iret bug in xen

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] do_iret bug in xen
From: "Ashish Bijlani" <ashish.bijlani@xxxxxxxxx>
Date: Tue, 27 Nov 2007 17:41:24 -0500
Delivery-date: Tue, 27 Nov 2007 14:42:02 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=JnKKQEedqeFfOYmk4623b78YXpCLdfDNjydsi8FyMI0=; b=rB/JWXxkqkT0A4h0x/G7epexMNF45e9xXUMVeMq/6PRsZfgBIwKjwof+wRAk1VYXLVehJGbS1CkxPLMZFdVHoI3J93rs+b+SOKWhLmdM9/KEIDFmO3GBtqGaiJ56d60YHj7huo2cM4iGZwkm6zVAKOqArQtiFYzSQSd+XlHTT08=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=HGBaNAAwp93Gs3kp31VZw5s8723awu9ZuqUmYRQqSocqhrcutbDncmdjEwNFODe8EfYUkEnX9tr7YrEGTAcr3Y9Ks8vroZ5uYusP+/v5ULXTulbRdOYlK4KNDCDotSXKbwDlwJgFkVoVOJdPFL7BSuwMQLrEDGIHMIlbToOerwI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <474C912B.2040401@xxxxxxxxxxxxxx>
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>
References: <E1Ix7Vw-000810-RL@host-192-168-0-1-bcn-london> <474C912B.2040401@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
"cpumask_raise_softirq(mask, SCHEDULE_SOFTIRQ)" sends an IPI to the target processor, this can cause current to change.

On Nov 27, 2007 4:50 PM, Andres Lagar-Cavilla < andreslc@xxxxxxxxxxxxxx> wrote:
raise_softirq is not the same as actually doing it. Raise only sets a
bit indicating pending softirq. Before returning to the guest, the bin
triggers actual execution of the softirq

Andres

   since "sti" is on, an interrupt can occur which can cause the
   control to enter "__runq_tickle", which then invokes
   "cpumask_raise_softirq(mask, SCHEDULE_SOFTIRQ)" to send IPI to a
   processor causing the control to enter "__enter_scheduler" which
   changes the current.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>