Messages in this thread | ![/](/images/icornerl.gif) | | Subject | Re: [PATCH net-next V4 5/5] vhost: access vq metadata through kernel virtual address | From | Jason Wang <> | Date | Fri, 25 Jan 2019 10:33:02 +0800 |
| |
On 2019/1/24 下午12:53, Michael S. Tsirkin wrote: >>>> - How hard is it to figure out which mode uses which code. >> It's as simple as tracing __get_user() usage in vhost process? >> >> Thanks > Well there are now mtu notifiers etc etc. It's hardly as well > contained as that. > >
We can setup filter out exactly what sets of function that we wan to trace. E.g we can only trace the usage of __get_user() and invalidate_range_start(). This should be sufficient.
In the long run, we may want to have some tracepoints for vhost_net.
Thanks
| ![\](/images/icornerr.gif) |