[STYLE_FIX]

This commit is contained in:
Bamboo
2017-03-29 22:49:22 +00:00
parent 93cc22b289
commit 98963c60f6
2 changed files with 4 additions and 4 deletions

View File

@@ -37,7 +37,7 @@ c_handle_interrupt(int irq, int syscall)
/* Only grab the lock if we are not handeling 'int_remote_call_ipi' interrupt
* also flag this lock as IRQ lock if handling the irq interrupts. */
NODE_LOCK_IF(irq != int_remote_call_ipi,
irq >= int_irq_min && irq <= int_irq_max);
irq >= int_irq_min && irq <= int_irq_max);
c_entry_hook();

View File

@@ -75,9 +75,9 @@ static void ipiStallCoreCallback(bool_t irqPath)
/* The current thread is running as we would replace this thread with an idle thread.
* The instruction should be re-executed if we are in kernel to handle syscalls. However,
* 'ThreadState_Restart' does not always result in regenerating exception if we
* are in kernel to handle them, e.g. hardware single step exception.
* are in kernel to handle them, e.g. hardware single step exception.
* Also, thread in 'ThreadState_RunningVM' should remain in same state. */
if(thread_state_ptr_get_tsType(&NODE_STATE(ksCurThread)->tcbState) == ThreadState_Running) {
if (thread_state_ptr_get_tsType(&NODE_STATE(ksCurThread)->tcbState) == ThreadState_Running) {
setThreadState(NODE_STATE(ksCurThread), ThreadState_Restart);
}
@@ -119,7 +119,7 @@ static void ipiStallCoreCallback(bool_t irqPath)
}
static void handleRemoteCall(IpiModeRemoteCall_t call, word_t arg0,
word_t arg1, word_t arg2, bool_t irqPath)
word_t arg1, word_t arg2, bool_t irqPath)
{
/* we gets spurious irq_remote_call_ipi calls, e.g. when handling IPI
* in lock while hardware IPI is pending. Guard against spurious IPIs! */