[Barrelfish-users] Deferred event problem...

Andrew Baumann Andrew.Baumann at microsoft.com
Fri Feb 28 22:28:17 CET 2014

Hi Mark,

This is not a known problem (at least not to me; someone else on the list might know more). Deferred events run off the same per-core timer used by the kernel for scheduling - on x86, this is the local APIC timer. If they don't work on other cores, then I would expect that a lot of scheduling code would also be broken. What platform are you running on? Does this reproduce on Qemu?


From: M Brown [mailto:M.Brown at huawei.com]
Sent: Thursday, 27 February 2014 18:15
To: barrelfish-users at lists.inf.ethz.ch
Cc: debashis bhattacharya
Subject: [Barrelfish-users] Deferred event problem...

   I'm running into a problem with the deferred event support. I'm running a system with 4 cores. When I attach a periodic deferred event (timer) within core 0 all works well. When I attach one within core 3 it does not fire at all. All deferred events are attached to their respective default waitsets and the "main"s running in each core are running an event loop on the core's respective default waitset. Is there any known problem with this function?

Mark Brown
Huawei Technologies Inc.
5340 Legacy Dr., Suite 175
Plano, TX 75024
Tel: 469-277-5700 x5870
Email: m.brown at huawei.com<mailto:m.brown at huawei.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.inf.ethz.ch/pipermail/barrelfish-users/attachments/20140228/382aefcd/attachment.html 

More information about the Barrelfish-users mailing list