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] disabling irqs in a non-preemptive OS

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] disabling irqs in a non-preemptive OS
From: Matthew Fioravante <Matthew.Fioravante@xxxxxxxxxx>
Date: Sun, 03 Jan 2010 12:08:15 -0500
Cc:
Delivery-date: Sun, 03 Jan 2010 09:13:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7636A87.557C%keir.fraser@xxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C7636A87.557C%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.23 (X11/20090817)
That I didn't realize. Now it makes sense, thanks!

Keir Fraser wrote:
On 31/12/2009 23:16, "Matthew Fioravante" <Matthew.Fioravante@xxxxxxxxxx>
wrote:

mini-os is a uniprocessor and non-preemptive OS so unless your thread
blocks, an irq handler (in this case event channel handler) will never
be run and thus won't be able to touch your critical sections.

What makes you think that? 'Non-preemptive' doesn't mean that you can't be
interrupted by irq context. That's why they're called interrupts!

 -- Keir



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

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