- 04 Dec, 2017 40 commits
-
-
Harry Wentland authored
C++ compilers don't like the implicit conversion Signed-off-by:
Harry Wentland <harry.wentland@amd.com> Reviewed-by:
Andrey Grodzovsky <Andrey.Grodzovsky@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Yue Hin Lau authored
removing duplicate functions, renaming struct mi_regs, etc. Signed-off-by:
Yue Hin Lau <Yuehin.Lau@amd.com> Reviewed-by:
-
Harry Wentland authored
Remove defines we no longer need Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Mikita Lipski authored
Registers added to definition list that are required for multi display synchronization Signed-off-by:
Mikita Lipski <mikita.lipski@amd.com> Reviewed-by:
Tony Cheng <Tony.Cheng@amd.com> Acked-by:
-
Yongqiang Sun authored
Program cursor attributes during set mode is only needed in case of pipe slipt, bottom pipe should be programmed same as top pipe. Need to program if address is 0. Signed-off-by:
Yongqiang Sun <yongqiang.sun@amd.com> Reviewed-by:
-
Yongqiang Sun authored
Moved lock and unlock to apply_ctx_to_surface, since all the front end programming is within apply_ctx_to_surface. Signed-off-by:
-
Anthony Koo authored
Some features should only be enabled on APUs or should not be enabled on APUs. Signed-off-by:
Anthony Koo <anthony.koo@amd.com> Reviewed-by:
-
Rex Zhu authored
the variable ref_clock was assigned same value twice in same function. Reviewed-by:
Rex Zhu <Rex.Zhu@amd.com> Signed-off-by:
-
Rex Zhu authored
Reviewed-by:
-
Rex Zhu authored
Used to set up smu power logging. Reviewed-by:
-
Rex Zhu authored
Used to set up smu power logging. Reviewed-by:
-
Rex Zhu authored
move powerplay and amdgpu shared structures and definitions to kgd_pp_interface.h. This is the interface between the base driver and powerplay. Acked-by:
-
Rex Zhu authored
Clean up the interface. Acked-by:
-
Rex Zhu authored
those functions are exported to DC Reviewed-by:
-
Rex Zhu authored
Move the display/power interfaces to one place. Reviewed-by:
-
Christian König authored
We always use the BO mem now. v2: minor rebase Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Michel Dänzer <michel.daenzer@amd.com> Signed-off-by:
-
Christian König authored
Display can't seem to handle this correctly. Signed-off-by:
-
Christian König authored
We need to test if any domain fits, not all of them. Signed-off-by:
-
Christian König authored
We always need to bind pinned BOs, not just when the caller requested the address. Signed-off-by:
-
Christian König authored
This allows us to specify multiple possible placements again. Signed-off-by:
-
pding authored
The exclusive mode has real-time limitation in reality, such like being done in 300ms. It's easy observed if running many VF/VMs in single host with heavy CPU workload. If we find the init fails due to exclusive mode timeout, try it again. v2: - rewrite the condition for readable value. v3: - fix typo, add comments for sleep Acked-by:
pding <Pixel.Ding@amd.com> Signed-off-by:
-
pding authored
Reviewed-by:
Monk Liu <monk.liu@amd.com> Signed-off-by:
-
Evan Quan authored
Signed-off-by:
Evan Quan <evan.quan@amd.com> Reviewed-by:
-
pding authored
Driver can use this interface to check if there's a function level reset done in hypervisor. It's helpful when IRQ handler for reset is not ready, or special handling is required. Acked-by:
-
pding authored
MMIO space can be blocked on virtualised device. Add this function to check if MMIO is blocked or not. Todo: need a reliable method such like communation with hypervisor. v2: - add comments inline Signed-off-by:
-
pding authored
Normally all waiting get timeout if there's one. Release the lock and return immediately when timeout happens. v2: - set the se_sh to broadcase before return Acked-by:
-
pding authored
When this VF stays in exclusive mode for long, other VFs will be impacted. The redundant messages causes exclusive mode timeout when they're redirected. That is a normal use case for cloud service to redirect guest log to virtual serial port. Reviewed-by:
-
Monk Liu authored
this query will give flag bits to indicate what happend on the given context Signed-off-by:
-
Monk Liu authored
reset_counter marks the reset counter number once the context is created, shouldn't be changed due to query. To keep U/K interface on the ctx_query and keep ctx's reset_counter logic compatible with GPU RESET feature, now use another var named "reset_counter_query" to replace the original checked & updated in amdgpu_ctx_query. Signed-off-by:
-
Andrey Grodzovsky authored
Signed-off-by:
-
Andrey Grodzovsky authored
Bug: Kfifo is limited at size, during GPU reset it would fill up to limit and the pushing thread (producer) would wait for the scheduler worker to consume the items in the fifo while holding reservation lock on a BO. The gpu reset thread on the other hand blocks the scheduler during reset. Before it unblocks the sceduler it might want to recover VRAM and so will try to reserve the same BO the producer thread is already holding creating a deadlock. Fix: Switch from kfifo to SPSC queue which is unlimited in size. Signed-off-by:
-
Andrey Grodzovsky authored
It is intended to sabstitute the bounded fifo we are currently using. Signed-off-by:
-
Monk Liu authored
merge the setting guilty on context into this function to avoid implement extra routine. v2: go through entity list and compare the fence_ctx before operate on the entity, otherwise the entity may be just a wild pointer Signed-off-by:
Chunming Zhou <David1.Zhou@amd.com> Signed-off-by:
-
Monk Liu authored
Signed-off-by:
-
Monk Liu authored
this way the real interested guilty is connected to entity->guilty pointer, and we can use entity->pointer later in gpu recovery procedure Signed-off-by:
-
Monk Liu authored
this member will be used later, it will points to the real var inside of context and CS_SUBMIT & gpu schdduler can decide if skip a job depends on context->guilty or *entity->guilty Signed-off-by:
-
Monk Liu authored
since gpu_scheduler source domain cannot access amdgpu variable so need create the hang_limit membewr for sched, and it can refer it for the upcoming GPU RESET patches v2: make hang_limit a parameter of sched_init() Signed-off-by:
-
Monk Liu authored
cleanups, now only operate on the given ring Signed-off-by:
-
Andrey Grodzovsky authored
Bug: amdgpu_job_free_cb was accessing s_job->s_entity when the allocated amdgpu_ctx (and the entity inside it) were already deallocated from amdgpu_cs_parser_fini. Fix: Save job's priority on it's creation instead of accessing it from s_entity later on. Signed-off-by:
Andres Rodriguez <andresx7@gmail.com> Signed-off-by:
-
