Skip to content

Conversation

@kitlith
Copy link
Contributor

@kitlith kitlith commented Oct 27, 2019

Fixes #471.

This involves creating a newtype wrapper around spin::Mutex to check when locking if the number of interrupts being serviced is currently zero.

@kitlith
Copy link
Contributor Author

kitlith commented Oct 27, 2019

It looks like maybe I should fiddle with this a bit more if syscall context is not considered irq context. (Is it? It's the only 'interrupt' where interrupts are not disabled.) maybe add an extra thing to the macro?

@Orycterope
Copy link
Member

Orycterope commented Oct 27, 2019

Indeed, syscall context isn't interrupt context 😕

@kitlith
Copy link
Contributor Author

kitlith commented Oct 27, 2019

Thanks for the feedback, I'll try to get to that today. Fixing syscall context in particular is going to be annoying (but that'll also lay the groundwork for switching back to counter-based SpinLockIRQ, i think.)

@roblabla
Copy link
Member

LGTM, can get merged after a rebase :)

Fixes sunriseos#471.

This involves creating a newtype wrapper around spin::Mutex to
check when locking if the number of interrupts being services is
currently zero.
@roblabla roblabla merged commit 9c9b8d6 into sunriseos:master Oct 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Detect usage of SpinLock in IRQ context

3 participants