|
From: John R. <jr...@bi...> - 2011-06-10 13:44:36
|
On 06/10/2011 05:38 AM, Igmar Palsenberg wrote: > > On Jun 9, 2011, at 5:04 PM, John Reiser wrote: > >>> ==1019== Warning: noted but unhandled ioctl 0xae03 with no size/direction hints >>> ==1019== This could cause spurious value errors to appear. >>> ==1019== See README_MISSING_SYSCALL_OR_IOCTL for guidance on >>> writing a proper wrapper. >> The syscall is: >> ioctl(fd, 0xae03, ...) Igmar Palsenberg <mai...@pa...> writes: > I would bet my money on KVM_CHECK_EXTENSION. The KVM ioctl() from what I can remember is two dozens of ioctl()'s, so if no one else volenteers, I'm willing to supply a patch for this. That is, if Oleg can somehow confirm that this really is KVM. linux/include/linux/kvm.h has ----- #define KVMIO 0xAE #define KVM_CHECK_EXTENSION _IO(KVMIO, 0x03) ----- and in this particular case there are only two arguments used by the ioctl, so the valgrind Warning is just a warning: the ioctl does not access user address space. -- |