Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind?

[Julian S. <js...@ac...>]

> One question to you: does it make sense to be hard-coding the *0x30000001*
> case into the generalioctl handler, or should there be an NVIDIA-specific
> file in the coregrind/m_syswrap directory?

There is already a mechanism for dealing with proprietary GPU ioctls,
because of the need to run on phones with various GPUs.  Try grepping
the sources (trunk) for "KernelVariant_android_gpu_adreno3xx" and follow
your nose from there.

Presumably you'll need to add a KernelVariant_<blah>_nvidia_<blah> enum
and a --kernel-variant= sub-flag.  Have a look at m_main.c:714.

J