From: harry <harry@hebutterworth.freeserve.co.uk>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Jacob Gorm Hansen <jacobg@diku.dk>
Subject: Re: errno i xs_wire.h
Date: Tue, 08 Nov 2005 13:38:28 +0000 [thread overview]
Message-ID: <1131457108.5970.20.camel@localhost.localdomain> (raw)
In-Reply-To: <200511081325.18626.mark.williamson@cl.cam.ac.uk>
I was talking with Rusty about this and apparently posix doesn't
actually standardise the numbers.
On Tue, 2005-11-08 at 13:25 +0000, Mark Williamson wrote:
> > 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)
>
> Isn't the basic set of errno vals posix standardised? So even if a guest OS
> doesn't deal in errnos itself, it can just import the BSD errno.h or
> similar...?
>
> Cheers,
> Mark
>
> > 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@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-11-08 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 12:04 errno i xs_wire.h Jacob Gorm Hansen
2005-11-08 12:20 ` harry
2005-11-08 12:22 ` Ewan Mellor
2005-11-08 13:25 ` Mark Williamson
2005-11-08 13:38 ` harry [this message]
2005-11-08 18:26 ` Oleg Goldshmidt
-- strict thread matches above, loose matches on Subject: below --
2005-11-08 21:59 Everhart, Craig
2005-11-09 12:06 ` Keir Fraser
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=1131457108.5970.20.camel@localhost.localdomain \
--to=harry@hebutterworth.freeserve.co.uk \
--cc=jacobg@diku.dk \
--cc=mark.williamson@cl.cam.ac.uk \
--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.