Otherwise it's impossible to know the reason for a fault or blob rejection
inside the automation.
While at it, also change return code of incorrect invokation to EINVAL.
Signed-off-by: Igor Druzhinin <igor.druzhi...@citrix.com>
---
Changes in v2:
- simply call "return errno". On Linux that seems to be safe as values <=255
are correctly propagated, on non-Linux I couldn't find error codes >127.
- return positive value on incorrect invokation
---
tools/misc/xen-ucode.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tools/misc/xen-ucode.c b/tools/misc/xen-ucode.c
index 0c257f4..409cace 100644
--- a/tools/misc/xen-ucode.c
+++ b/tools/misc/xen-ucode.c
@@ -25,7 +25,7 @@ int main(int argc, char *argv[])
fprintf(stderr,
"xen-ucode: Xen microcode updating tool\n"
"Usage: %s <microcode blob>\n", argv[0]);
- return 0;
+ return EINVAL;
}
filename = argv[1];
@@ -62,8 +62,11 @@ int main(int argc, char *argv[])
ret = xc_microcode_update(xch, buf, len);
if ( ret )
+ {
fprintf(stderr, "Failed to update microcode. (err: %s)\n",
strerror(errno));
+ return errno;
+ }
xc_interface_close(xch);
--
2.7.4
