diff options
| author |   Matthew Brost <matthew.brost@intel.com> | 2021-10-14 10:19:50 -0700 |
|---|---|---|
| committer |   John Harrison <John.C.Harrison@Intel.com> | 2021-10-15 10:37:38 -0700 |
| commit | 09c5e3a5e509bb10249c8252dc10c0d8a842e4ae (patch) | |
| tree | b138b17da70b3b9a949287447a2a468ae324bc90 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | drm/i915/guc: Ensure GuC schedule operations do not operate on child contexts (diff) | |
| download | wireguard-linux-09c5e3a5e509bb10249c8252dc10c0d8a842e4ae.tar.xz wireguard-linux-09c5e3a5e509bb10249c8252dc10c0d8a842e4ae.zip | |
drm/i915/guc: Assign contexts in parent-child relationship consecutive guc_ids
Assign contexts in parent-child relationship consecutive guc_ids. This
is accomplished by partitioning guc_id space between ones that need to
be consecutive (1/16 available guc_ids) and ones that do not (15/16 of
available guc_ids). The consecutive search is implemented via the bitmap
API.
This is a precursor to the full GuC multi-lrc implementation but aligns
to how GuC mutli-lrc interface is defined - guc_ids must be consecutive
when using the GuC multi-lrc interface.
v2:
(Daniel Vetter)
- Explicitly state why we assign consecutive guc_ids
v3:
(John Harrison)
- Bring back in spin lock
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20211014172005.27155-11-matthew.brost@intel.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions