-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[qemu-usermode] Simplify safe syscall patches. #1
base: master
Are you sure you want to change the base?
Conversation
#define QEMU_H | ||
|
||
-#include "hostdep.h" | ||
+// #include "hostdep.h" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case it is just remove that line. I would make sense to explain this better as this change applies to any use of qemu since it not only applies to sb2.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it's required, because it'll redirect the syscall to an assembly implementation otherwise and sb2 can't handle that. The explanation is in the spec file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally speaking, I'm a firm believer of the "there shouldn't be commented code" rule. But I think this just might be the exception. But I also think Thaodan has a point - not everyone is going to go read the spec file to find the explanation here. Replacing this with // #include "hostdep.h" commented out because sb2 handles syscalls going through c interface
or something like that would make it clear. Bit this is all just nitpicking really.
Frajo ***@***.***> writes:
Yes it's required, because it'll redirect the syscall to an assembly implementation otherwise and sb2 can't handle that. The explanation is in the spec file.
It's worth to put it here since the code might be used without the spec
file and the context should be in the patch for rebasing etc.
|
LGTM, except for the WIP in title, and the nitpick about the commented out include |
After sailfishos/scratchbox2#21 is merged, we can now let syscalls go through the C syscall function.
After sailfishos/scratchbox2#21
is merged, we can now let syscalls go through the C syscall
function.
DO NOT MERGE BEFORE:
sailfishos/scratchbox2#21