Use `unlikely()` to error checking conditions about unikraft HOT 6 OPEN

@pranjalrai4 , unlikely is typically used for error conditions. Whenever there is something that results in ending the current function / flow, that's probably a condition to be wrapped with unlikely. It's not a rule, but it's often the case.

from unikraft.

Hi! I am a Computer Science student at the University of Texas at Austin. I am currently taking virtualization (CS 360v) and I would like to contribute to this project. I saw this issue opened up last year and I would like to work on it, but I was wondering if it was still open.

from unikraft.

Sure, @pranjalrai4 , go for it.

from unikraft.

@razvand How do we know if an error is unlikely()? Also, would we need to do this for every file in the codebase or do we need to do this for a subset of files?

from unikraft.

@razvand What is the selector and component for this issue? I want to confirm before committing our changes : )

from unikraft.

@ggracechoi , if it touches multiple libraries, use lib/* as the selector.

from unikraft.