Michael S. Tsirkin wrote: > Remove in_range from kvm_io_device and ask read/write callbacks, if > supplied, to perform range checks internally. This allows aliasing > (mostly for in-kernel virtio), as well as better error handling by > making it possible to pass errors up to userspace. And it's enough to > look at the diffstat to see that it's a better API anyway. > > While we are at it, document locking rules for kvm_io_device. > Hi Michael, I just tried to apply this to kvm.git/master, and it blew up really badly. What tree should I be using? -Greg
Attachment:
signature.asc
Description: OpenPGP digital signature
