3 Commits

Author	SHA1	Message	Date
Debarshi Dutta	200777b854	gpu: nvgpu: bvec for channel and tsg ... Below changes are added. 1) Added checks in nvgpu_channel_from_id__func, nvgpu_tsg_check_and_get_from_id 2) Added BVEC tests for nvgpu_channel_open_new, nvgpu_channel_from_id, nvgpu_tsg_check_and_get_from_id, nvgpu_tsg_set_error_notifier 3) Added common function get_random_u32. Jira NVGPU-6905 Change-Id: I374d6f5503dc05e3224213d772a1752d82cbdc91 Signed-off-by: Debarshi Dutta <ddutta@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvgpu/+/2548304 (cherry picked from commit 39b2529b3e96cfd3cbd3bb020f32ee2cca0ea363) Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvgpu/+/2554021 Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> Reviewed-by: svc_kernel_abi <svc_kernel_abi@nvidia.com> Reviewed-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: Vaibhav Kachore <vkachore@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit	2021-07-07 12:25:50 -07:00
Alex Waterman	5f0fdf085c	nvgpu: unit: Add new mock register framework ... Many tests used various incarnations of the mock register framework. This was based on a dump of gv11b registers. Tests that greatly benefitted from having generally sane register values all rely heavily on this framework. However, every test essentially did their own thing. This was not efficient and has caused a some issues in cleaning up the device and host code. Therefore introduce a much leaner and simplified register framework. All unit tests now automatically get a good subset of the gv11b registers auto-populated. As part of this also populate the HAL with a nvgpu_detect_chip() call. Many tests can now _probably_ have all their HAL init (except dummy HAL stuff) deleted. But this does require a few fixups here and there to set HALs to NULL where tests expect HALs to be NULL by default. Where necessary HALs are cleared with a memset to prevent unwanted code from executing. Overall, this imposes a far smaller burden on tests to initialize their environments. Something to consider for the future, though, is how to handle supporting multiple chips in the unit test world. JIRA NVGPU-5422 Change-Id: Icf1a63f728e9c5671ee0fdb726c235ffbd2843e2 Signed-off-by: Alex Waterman <alexw@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvgpu/+/2335334 Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>	2020-12-15 14:13:28 -06:00
Vedashree Vidwans	0ca906a6ad	gpu: nvgpu: unit: fifo: fifo unit test ... This unit test covers most of the nvgpu.common.fifo.fifo module lines and almost all branches. Jira NVGPU-3697 Change-Id: I5722277a3e1630a902f63b707eb3de1c4e1876b0 Signed-off-by: Vedashree Vidwans <vvidwans@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/2237796 Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>	2020-12-15 14:10:29 -06:00