From: Gerd Hoffmann <kraxel@suse.de>
To: xen-devel@lists.xensource.com
Subject: [patch] Add more xc_error_code values.
Date: Fri, 08 Dec 2006 17:16:43 +0100 [thread overview]
Message-ID: <20061208161634.203794000@suse.de> (raw)
[-- Attachment #1: tools-add-errors.diff --]
[-- Type: text/plain, Size: 1328 bytes --]
XC_INVALID_PARAM
such as asking for features unsupported by either xen or guest kernel.
XC_OUT_OF_MEMORY
no comment ;)
With description texts this time.
Signed-off-by: Gerd Hoffmann <kraxel@suse.de>
---
tools/libxc/xc_private.c | 4 ++++
tools/libxc/xenctrl.h | 2 ++
2 files changed, 6 insertions(+)
Index: build-32-unstable-12809/tools/libxc/xenctrl.h
===================================================================
--- build-32-unstable-12809.orig/tools/libxc/xenctrl.h
+++ build-32-unstable-12809/tools/libxc/xenctrl.h
@@ -691,6 +691,8 @@ typedef enum {
XC_ERROR_NONE = 0,
XC_INTERNAL_ERROR = 1,
XC_INVALID_KERNEL = 2,
+ XC_INVALID_PARAM = 3,
+ XC_OUT_OF_MEMORY = 4,
} xc_error_code;
#define XC_MAX_ERROR_MSG_LEN 1024
Index: build-32-unstable-12809/tools/libxc/xc_private.c
===================================================================
--- build-32-unstable-12809.orig/tools/libxc/xc_private.c
+++ build-32-unstable-12809/tools/libxc/xc_private.c
@@ -45,6 +45,10 @@ const char *xc_error_code_to_desc(int co
return "Internal error";
case XC_INVALID_KERNEL:
return "Invalid kernel";
+ case XC_INVALID_PARAM:
+ return "Invalid configuration";
+ case XC_OUT_OF_MEMORY:
+ return "Out of memory";
}
return "Unknown error code";
--
next reply other threads:[~2006-12-08 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 16:16 Gerd Hoffmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-08 15:09 [patch] Add more xc_error_code values Gerd Hoffmann
2006-12-08 15:35 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061208161634.203794000@suse.de \
--to=kraxel@suse.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.