Re: [RFC v1 2/2] vfio-ccw: Don't exit early if state of the vfio-ccw subchannel is not idle

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

 



On Tue, 22 Jan 2019 17:35:36 +0100
Halil Pasic <pasic@xxxxxxxxxxxxx> wrote:

> On Tue, 22 Jan 2019 10:19:29 -0500
> Farhan Ali <alifm@xxxxxxxxxxxxx> wrote:
> 
> > > I would also like to see the error codes, which are:
> > > * obviously a substantial part of the interface, and need to be mapped
> > >    to channel IO conditions, and thus
> > > * beyond usual file IO stuff (i.e. man 3 write won't give you the right
> > >    explanation for the error codes
> > > properly documented. @Farhan: Would you like to tackle this one?
> > >    
> > 
> > Are you suggesting documenting the mapping of the error codes in the 
> > vfio-ccw doc? I could do that, but I fear the doc wouldn't be updated as 
> > often.  
> 
> The other option would be the uapi header file. We talk about an uapi
> interface, which I hope we don't want to change/extend too often. Thus
> my hope is that the documentation of the error codes won't need any
> updating.
> 
> @Connie do you have an opinion?

If I were to implement a userspace exploiter of this interface, I'd
probably look into the uapi header files.



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux