From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Stefano Stabellini <stefano@aporeto.com>
Cc: jgross@suse.com, lars.kurth@citrix.com, wei.liu2@citrix.com,
andrew.cooper3@citrix.com, Paul.Durrant@citrix.com,
xen-devel@lists.xenproject.org, joao.m.martins@oracle.com,
boris.ostrovsky@oracle.com, roger.pau@citrix.com
Subject: Re: [DOC v8] PV Calls protocol design
Date: Mon, 30 Jan 2017 09:33:15 +0200 [thread overview]
Message-ID: <5e74fb32-b2e5-11e6-7f9b-3b6cc7f0f68c@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1701271040390.2884@sstabellini-ThinkPad-X260>
On 01/27/2017 08:48 PM, Stefano Stabellini wrote:
> On Fri, 27 Jan 2017, Oleksandr Andrushchenko wrote:
>> Hi, Stefano!
>>> #### Error numbers
>>>
>>> The numbers corresponding to the error names specified by POSIX are:
>>>
>>> [EPERM] -1
>>> [ENOENT] -2
>>>
>> Don't you want to use Xen's errno.h here as described in [1]?
>> So we have error codes consistent for all PV protocols?
>>
>> Thanks,
>> Oleksandr
>>
>> [1] https://marc.info/?l=xen-devel&m=148545604312317&w=2
>>
> Hi Oleksandr,
>
> PVCalls is a bit different, because the protocol is meant to send POSIX
> calls to the backend, therefore, I have to use POSIX error names in the
> protocol.
>
> I could assign any numbers to the names though. It makes sense to use
> the Xen/Linux error numbers for simplicity. Whether I declare them
> directly as numbers as I have done here, or indirectly as XEN_ERRNO, I
> don't think it matters much. But I think that using numbers is clearer,
> that's why I did it that way.
got it, thanks
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-30 7:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 0:14 [DOC v8] PV Calls protocol design Stefano Stabellini
2017-01-27 7:08 ` Oleksandr Andrushchenko
2017-01-27 18:48 ` Stefano Stabellini
2017-01-30 7:33 ` Oleksandr Andrushchenko [this message]
2017-02-07 20:24 ` Konrad Rzeszutek Wilk
2017-02-10 1:29 ` Stefano Stabellini
2017-02-10 18:44 ` Konrad Rzeszutek Wilk
2017-02-10 20:09 ` Stefano Stabellini
2017-02-10 21:30 ` Konrad Rzeszutek Wilk
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=5e74fb32-b2e5-11e6-7f9b-3b6cc7f0f68c@gmail.com \
--to=andr2000@gmail.com \
--cc=Paul.Durrant@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=joao.m.martins@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=roger.pau@citrix.com \
--cc=stefano@aporeto.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).