tap: tap as an independent module - net-next.git - net-next plumbings

summary refs log tree commit diff

path: root/include/trace/events/random.h

diff options

author	Sainath Grandhi <sainath.grandhi@intel.com>	2017-02-10 16:03:51 -0800
committer	David S. Miller <davem@davemloft.net>	2017-02-11 20:59:41 -0500
commit	9a393b5d5988ea4eaa3e0da138321abe0dc03a68 (patch)
tree	5a006ee32965ff9c76984aa7ce7c870d966be7ac /include/trace/events/random.h
parent	d9f1f61c0801a73ff36d416a7ede54229b231e1d (diff)

tap: tap as an independent module

This patch makes tap a separate module for other types of virtual interfaces, for example, ipvlan to use. Signed-off-by: Sainath Grandhi <sainath.grandhi@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>

Diffstat (limited to 'include/trace/events/random.h')

0 files changed, 0 insertions, 0 deletions

quiring a different lock than `dma_pl330_rqcb'. NOTE that, as a result, `pl330_free_chan_resources' executes `list_splice_tail_init' on `pch->work_list' under lock `pl330->lock', whereas in the rest of the code `pch->work_list' is protected by `pch->lock'. I don't know if this may cause race conditions. Similarly `pch->cyclic' is written by `pl330_alloc_chan_resources' under `pl330->lock' but read by `pl330_tx_submit' under `pch->lock'. Second, I have removed locking from `pl330_request_channel' and `pl330_release_channel' functions. Function `pl330_request_channel' is only called from `pl330_alloc_chan_resources', so the lock is already held. Function `pl330_release_channel' is called from `pl330_free_chan_resources', which already holds the lock, and from `pl330_del'. Function `pl330_del' is called in an error path of `pl330_probe' and at the end of `pl330_remove', but I assume that there cannot be concurrent accesses to the protected data at those points. Signed-off-by: Iago Abal <mail@iagoabal.eu> Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>

Diffstat (limited to 'tools/testing/selftests/timers/set-tz.c')