Searched refs:agents (Results 1 – 3 of 3) sorted by relevance
12 struct mlx5_hv_vhca_agent *agents[MLX5_HV_VHCA_AGENT_MAX]; member81 struct mlx5_hv_vhca_agent *agent = hv_vhca->agents[i]; in mlx5_hv_vhca_invalidate_work()120 struct mlx5_hv_vhca_agent *agent = hv_vhca->agents[i]; in mlx5_hv_vhca_agents_control()138 struct mlx5_hv_vhca_agent *agent = hv_vhca->agents[i]; in mlx5_hv_vhca_capabilities()220 hv_vhca->agents[MLX5_HV_VHCA_AGENT_CONTROL] = agent; in mlx5_hv_vhca_init()233 agent = hv_vhca->agents[MLX5_HV_VHCA_AGENT_CONTROL]; in mlx5_hv_vhca_cleanup()239 WARN_ON(hv_vhca->agents[i]); in mlx5_hv_vhca_cleanup()270 if (hv_vhca->agents[type]) { in mlx5_hv_vhca_agent_create()288 hv_vhca->agents[type] = agent; in mlx5_hv_vhca_agent_create()302 if (WARN_ON(agent != hv_vhca->agents[agent->type])) { in mlx5_hv_vhca_agent_destroy()[all …]
897 to prohibit certain system agents from accessing memory with 1 KiB901 by hardware agents inside the SoC. Read and write masks can be
42 of agents, it will only get those on that LM. Each LM is completely isolated1271 settings/actions that must be exposed from the SM to agents. They are device
Completed in 10 milliseconds