This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] libxen-3.0 (libxc rewrite)

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] libxen-3.0 (libxc rewrite)
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Tue, 22 Mar 2005 16:39:31 +0000
Cc: Nivedita Singhvi <niv@xxxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Christian.Limpach@xxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxxx, ian.pratt@xxxxxxxxxxxx
Delivery-date: Wed, 23 Mar 2005 16:19:24 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Your message of "Tue, 22 Mar 2005 10:34:11 CST." <42404903.30900@xxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> Nivedita Singhvi wrote:
> > Anthony Liguori wrote:
> >
> >> There's only one problem with this: thread-safety.  I believe errno 
> >> is commonly implemented in thread-local storage.  We'd have to jump 
> >> through major hoops to get our own proper errno.
> >
> >
> > Anthony - not sure what you are referring to here, because
> > the common use is to use the global errno made available
> > in libc. Is that not a proper errno?
> Some libraries implement their own psuedo-errno to store library 
> specific errors.  To the best of my knowledge, with the exception of 
> system libraries (libc) errno is not used and not really supposed to be 
> used.
> I could be wrong, but I can't think of any libraries that use it.

I think we can just use the regular errno as defined in errno.h (and
in the Posix standard). 

The convention of using negative numbers in the kernel is
counterbalanced by another convention of using positive numbers 
in user space. Shouldn't be too hard to fix I guess. 



This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
Xen-devel mailing list