[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] do_iret bug in xen
- To: xen-devel@xxxxxxxxxxxxxxxxxxx
- 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
- 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=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
"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
|
