On Sun, Jun 14, 2015 at 01:12:45PM +0200, Patrik Jakobsson wrote: [...] > How about adding a "void *private" field to struct tcb. That way any > syscall can store additional data across the life of the tcb. We can add a field to struct tcb, but its semantics wrt memory management should be strictly defined. For example, who is responsible for memory deallocation, what droptcb() should do about this field, etc. In this case, we probably need to store a pointer to a string dynamically allocated in drm_get_driver_name() (on entering syscall) which is automatically deallocated later in trace_syscall_exiting() and droptcb(). -- ldv
Attachment:
pgpKVJhFA0ad4.pgp
Description: PGP signature
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
