[Barrelfish-users] Fwd: Interrupt Handlers

Piyus Kedia piyuskedia at gmail.com
Thu Aug 1 22:46:36 CEST 2013


I am working on Kernel Binary Translator which pushes the translated PC
instead of the original PC on the stack when an interrupt or exception
occurs while executing in kernel mode. There could be some problem if the
interrupt or exception handler uses the PC value pushed on the stack. Since
interrupts are disabled in kernel mode this problem won't exist. But still
some exceptions like page fault can occur in kernel mode. I just want to
make sure that these handlers don't use the PC value from the stack or
don't overwrite the return address on the stack.


On Fri, Aug 2, 2013 at 4:20 AM, Timothy Roscoe <troscoe at inf.ethz.ch> wrote:

> As Andrew says, the Barrelfish CPU driver processes all exceptions
> (whether hardware interrupts or traps) serially with interrupts disabled,
> unless it's idling.
> Note that (like K42 and Psyche) Barrelfish uses upcall dispatch most of
> the time (think Scheduler Activations), so exit from an exception handler
> is typically a jump to a completely different IP/PC value from when that
> (or any other) exception occurred.
> Note also that Barrelfish doesn't have any kernel threads - each CPU
> driver has a single, static, dedicated kernel stack.
> Could you say a little more about what you mean?
>  -- Mothy
> On 13-08-01 05:32 AM, Piyus Kedia wrote:
>> Hi All,
>> I am working on dynamic binary translator. Please tell me if anybody
>> know if in Barrelfish interrupted kernel PC is ever used in interrupt
>> handlers?
>> Thanks and regards,
>> Piyus
>> ______________________________**_________________
>> Barrelfish-users mailing list
>> Barrelfish-users at lists.inf.**ethz.ch <Barrelfish-users at lists.inf.ethz.ch>
>> https://lists.inf.ethz.ch/**mailman/listinfo/barrelfish-**users<https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.inf.ethz.ch/pipermail/barrelfish-users/attachments/20130802/884f1c71/attachment.html 

More information about the Barrelfish-users mailing list