As an information only. So Userspace can use this information and be able to correlate different GTs. Make API symmetric between Engine and GT info. There's no need right now to include a tile_query entry since there's no other information that we need from tile that is not already exposed through different queries. However, this could be added later if we have different Tile information that could matter to userspace. But let's keep the API ready for a direct reference to Tile ID based on the GT entry.
Showing the changes to include/uapi (1 of 2 files). Show all
Unified · Split
| @@ -378,6 +378,8 @@ struct drm_xe_gt { · 377 unmodified lines | |||
| 378 | #define DRM_XE_QUERY_GT_TYPE_MEDIA 1 | 378 | #define DRM_XE_QUERY_GT_TYPE_MEDIA 1 |
| 379 | /** @type: GT type: Main or Media */ | 379 | /** @type: GT type: Main or Media */ |
| 380 | __u16 type; | 380 | __u16 type; |
| 381 | /** @tile_id: Tile ID where this GT lives (Information only) */ | ||
| 382 | __u16 tile_id; | ||
| 381 | /** @gt_id: Unique ID of this GT within the PCI Device */ | 383 | /** @gt_id: Unique ID of this GT within the PCI Device */ |
| 382 | __u16 gt_id; | 384 | __u16 gt_id; |
| 383 | /** @reference_clock: A clock frequency for timestamp */ | 385 | /** @reference_clock: A clock frequency for timestamp */ |