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

Re: [Xen-devel] [DOC v8] PV Calls protocol design

To: Stefano Stabellini <stefano@xxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
From: Oleksandr Andrushchenko <andr2000@xxxxxxxxx>
Date: Fri, 27 Jan 2017 09:08:59 +0200
Cc: jgross@xxxxxxxx, lars.kurth@xxxxxxxxxx, wei.liu2@xxxxxxxxxx, andrew.cooper3@xxxxxxxxxx, Paul.Durrant@xxxxxxxxxx, joao.m.martins@xxxxxxxxxx, boris.ostrovsky@xxxxxxxxxx, roger.pau@xxxxxxxxxx
Delivery-date: Fri, 27 Jan 2017 07:09:23 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [DOC v8] PV Calls protocol design
  - From: Stefano Stabellini

References:
- [Xen-devel] [DOC v8] PV Calls protocol design
  - From: Stefano Stabellini

Prev by Date: Re: [Xen-devel] [PATCH] xen, input: try to read screen resolution for xen-kbdfront
Next by Date: [Xen-devel] [PATCH v2] xen, input: try to read screen resolution for xen-kbdfront
Previous by thread: [Xen-devel] [DOC v8] PV Calls protocol design
Next by thread: Re: [Xen-devel] [DOC v8] PV Calls protocol design
Index(es):
- Date
- Thread

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