Re: [Xen-devel] [PATCH RFC 4/6] xen: Print and use errno where applicable.

On Thu, Jul 02, 2015 at 12:00:29PM +0100, Stefano Stabellini wrote: > On Wed, 1 Jul 2015, Konrad Rzeszutek Wilk wrote: > > On Wed, Jul 01, 2015 at 02:01:07PM +0100, Stefano Stabellini wrote: > > > On Mon, 29 Jun 2015, Konrad Rzeszutek Wilk wrote: > > > > In Xen 4.6 commit cd2f100f0f61b3f333d52d1737

Re: [Xen-devel] [PATCH RFC 4/6] xen: Print and use errno where applicable.

On Wed, 1 Jul 2015, Konrad Rzeszutek Wilk wrote: > On Wed, Jul 01, 2015 at 02:01:07PM +0100, Stefano Stabellini wrote: > > On Mon, 29 Jun 2015, Konrad Rzeszutek Wilk wrote: > > > In Xen 4.6 commit cd2f100f0f61b3f333d52d1737dd73f02daee592 > > > "libxc: Fix do_memory_op to return negative value on er

Re: [Xen-devel] [PATCH RFC 4/6] xen: Print and use errno where applicable.

On Wed, Jul 01, 2015 at 02:01:07PM +0100, Stefano Stabellini wrote: > On Mon, 29 Jun 2015, Konrad Rzeszutek Wilk wrote: > > In Xen 4.6 commit cd2f100f0f61b3f333d52d1737dd73f02daee592 > > "libxc: Fix do_memory_op to return negative value on errors" > > made the libxc API less odd-ball: On errors, re

Re: [Xen-devel] [PATCH RFC 4/6] xen: Print and use errno where applicable.

On Mon, 29 Jun 2015, Konrad Rzeszutek Wilk wrote: > In Xen 4.6 commit cd2f100f0f61b3f333d52d1737dd73f02daee592 > "libxc: Fix do_memory_op to return negative value on errors" > made the libxc API less odd-ball: On errors, return value is > -1 and error code is in errno. On success the return value >

[Xen-devel] [PATCH RFC 4/6] xen: Print and use errno where applicable.

In Xen 4.6 commit cd2f100f0f61b3f333d52d1737dd73f02daee592 "libxc: Fix do_memory_op to return negative value on errors" made the libxc API less odd-ball: On errors, return value is -1 and error code is in errno. On success the return value is either 0 or an positive value. Since we could be runnin