[dpdk-dev] [PATCH] vfio: correct system call error checking

2014-06-17 Thread Richardson, Bruce
> -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > Sent: Tuesday, June 17, 2014 1:40 PM > To: Richardson, Bruce > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH] vfio: correct system call error checking > > On Tue, Jun 17,

[dpdk-dev] [PATCH] vfio: correct system call error checking

2014-06-17 Thread Richardson, Bruce
> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Neil Horman > Sent: Tuesday, June 17, 2014 12:04 PM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH] vfio: correct system call error checking > > Noticed today that ioctl error cod

[dpdk-dev] [PATCH] vfio: correct system call error checking

2014-06-17 Thread Neil Horman
On Tue, Jun 17, 2014 at 08:21:29PM +, Richardson, Bruce wrote: > > -Original Message- > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Neil Horman > > Sent: Tuesday, June 17, 2014 12:04 PM > > To: dev at dpdk.org > > Subject: [dpdk-dev] [PA

[dpdk-dev] [PATCH] vfio: correct system call error checking

2014-06-17 Thread Neil Horman
Noticed today that ioctl error code return checking was incorrect in some of the vfio code. ioctl can return a negative value if the system detects an error before the target device/driver can produce a return code. The dpdk vfio code only checks specfically for the values that it expects, which