[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] errno i xs_wire.h

To: xen-devel@xxxxxxxxxxxxxxxxxxx
From: Jacob Gorm Hansen <jacobg@xxxxxxx>
Date: Tue, 8 Nov 2005 13:04:33 +0100
Delivery-date: Tue, 08 Nov 2005 12:04:44 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ibcZJy3/NKT/x3k/xdyOG9xc/i0lfn2CZaSbO05iNzv3NcoESF54dcKlQHNth9EFbvbbcHf1Z7EtdqDDzQ7Lvc+0LQnFRTdrbJBEFPGB5J5UE3P2yCjVDXvhtnTbndDEcJcrkxdPg2j/44fG8R3G+Ffx6zGpZ7RA/UvkH2tzTm4=
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

hi,

playing with xenbus support in mini-os, I noticed that xs_wire.h
references errno constants such as EINVAL. Is the use of these
constants (which could be guest-OS specific) in the wire-protocol not
problematic? Should xs_wire.h define its own set of constants to be
used instead?

Jacob

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Follow-Ups:
- Re: [Xen-devel] errno i xs_wire.h
  - From: Mark Williamson
- Re: [Xen-devel] errno i xs_wire.h
  - From: Ewan Mellor
- Re: [Xen-devel] errno i xs_wire.h
  - From: harry

Prev by Date: [Xen-devel] Feature request: xm destroy/shutdown - multiple arguments
Next by Date: [Xen-devel] Maybe a bug of xen
Previous by thread: [Xen-devel] Feature request: xm destroy/shutdown - multiple arguments
Next by thread: Re: [Xen-devel] errno i xs_wire.h
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.