Add support for querying hw info that UMDs need
Subsystems (3)
v3 cover Add support for querying hw info that UMDs need
From: John Harrison <[email protected]>
Various UMDs require hardware configuration information about the current platform. A bunch of static information is available in a fixed table that can be retrieved from the GuC.
v2: Rebased to newer baseline and added a kerneldoc comment.
v3: Rebased to newer baseline and newer GuC interface.
Test-with: [email protected]
UMD: https://github.com/intel/compute-runtime/pull/432/files
UMD: https://github.com/intel/media-driver/pull/1239/files
John Harrison (1):
drm/i915/guc: Add fetch of hwconfig table
Rodrigo Vivi (1):
drm/i915/uapi: Add query for hwconfig table
drivers/gpu/drm/i915/Makefile | 1 + .../gpu/drm/i915/gt/uc/abi/guc_actions_abi.h | 1 + .../gpu/drm/i915/gt/uc/abi/guc_errors_abi.h | 4 + drivers/gpu/drm/i915/gt/uc/intel_guc.h | 3 + .../gpu/drm/i915/gt/uc/intel_guc_hwconfig.c | 151 ++++++++++++++++++ .../gpu/drm/i915/gt/uc/intel_guc_hwconfig.h | 19 +++ drivers/gpu/drm/i915/gt/uc/intel_uc.c | 6 + drivers/gpu/drm/i915/i915_query.c | 23 +++ include/uapi/drm/i915_drm.h | 1 + 9 files changed, 209 insertions(+) create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.h
Signature · 1 line
2.25.1
PATCH v3 1/2 drm/i915/guc: Add fetch of hwconfig table
From: John Harrison <[email protected]>
Implement support for fetching the hardware description table from the GuC. The call is made twice - once without a destination buffer to query the size and then a second time to fill in the buffer.
Note that the table is only available on ADL-P and later platforms.
--- drivers/gpu/drm/i915/Makefile | 1 + .../gpu/drm/i915/gt/uc/abi/guc_actions_abi.h | 1 + .../gpu/drm/i915/gt/uc/abi/guc_errors_abi.h | 4 + drivers/gpu/drm/i915/gt/uc/intel_guc.h | 3 + .../gpu/drm/i915/gt/uc/intel_guc_hwconfig.c | 151 ++++++++++++++++++ .../gpu/drm/i915/gt/uc/intel_guc_hwconfig.h | 19 +++ drivers/gpu/drm/i915/gt/uc/intel_uc.c | 6 + 7 files changed, 185 insertions(+) create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.h
drivers/gpu/drm/i915/Makefile +1 -0
@@ -193,6 +193,7 @@ i915-y += gt/uc/intel_uc.o \ gt/uc/intel_guc_rc.o \ gt/uc/intel_guc_slpc.o \ gt/uc/intel_guc_submission.o \ + gt/uc/intel_guc_hwconfig.o \ gt/uc/intel_huc.o \ gt/uc/intel_huc_debugfs.o \ gt/uc/intel_huc_fw.o
drivers/gpu/drm/i915/gt/uc/abi/guc_actions_abi.h +1 -0
@@ -129,6 +129,7 @@ enum intel_guc_action {INTEL_GUC_ACTION_ENGINE_FAILURE_NOTIFICATION =0x1009 ,INTEL_GUC_ACTION_SETUP_PC_GUCRC =0x3004 ,INTEL_GUC_ACTION_AUTHENTICATE_HUC =0x4000 , +INTEL_GUC_ACTION_GET_HWCONFIG =0x4100 ,INTEL_GUC_ACTION_REGISTER_CONTEXT =0x4502 ,INTEL_GUC_ACTION_DEREGISTER_CONTEXT =0x4503 , INTEL_GUC_ACTION_REGISTER_COMMAND_TRANSPORT_BUFFER = 0x4505,
drivers/gpu/drm/i915/gt/uc/abi/guc_errors_abi.h +4 -0
@@ -8,6 +8,10 @@enum intel_guc_response_status {INTEL_GUC_RESPONSE_STATUS_SUCCESS =0x0 , +INTEL_GUC_RESPONSE_NOT_SUPPORTED =0x20 , +INTEL_GUC_RESPONSE_NO_ATTRIBUTE_TABLE =0x201 , +INTEL_GUC_RESPONSE_NO_DECRYPTION_KEY =0x202 , +INTEL_GUC_RESPONSE_DECRYPTION_FAILED =0x204 ,INTEL_GUC_RESPONSE_STATUS_GENERIC_FAIL =0xF000 , };
drivers/gpu/drm/i915/gt/uc/intel_guc.h +3 -0
@@ -13,6 +13,7 @@#include "intel_guc_fw.h" #include "intel_guc_fwif.h" #include "intel_guc_ct.h" +#include "intel_guc_hwconfig.h" #include "intel_guc_log.h" #include "intel_guc_reg.h" #include "intel_guc_slpc_types.h"
@@ -37,6 +38,8 @@ struct intel_guc {struct intel_guc_ct ct;/** @slpc: sub-structure containing SLPC related data and objects */ struct intel_guc_slpc slpc; +/** @hwconfig: hardware configuration KLV table */ +struct intel_guc_hwconfig hwconfig;/** @sched_engine: Global engine used to submit requests to GuC */ struct i915_sched_engine *sched_engine;
drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c new file +151 -0
151 lines not on this page · raw message
drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.h new file +19 -0
@@ -0,0 +1,19 @@ +/* SPDX-License-Identifier: MIT */ +/* +* Copyright © 2021 Intel Corporation +*/ + +#ifndef _INTEL_GUC_HWCONFIG_H_ +#define _INTEL_GUC_HWCONFIG_H_ + +#include <linux/types.h> + +struct intel_guc_hwconfig { +u32 size; +void *ptr; +}; + +int intel_guc_hwconfig_init (struct intel_guc_hwconfig *hwconfig); +void intel_guc_hwconfig_fini (struct intel_guc_hwconfig *hwconfig); + +#endif /* _INTEL_GUC_HWCONFIG_H_ */
drivers/gpu/drm/i915/gt/uc/intel_uc.c +6 -0
@@ -503,6 +503,10 @@ static int __uc_init_hw(struct intel_uc *uc)if (ret) goto err_log_capture; + ret =intel_guc_hwconfig_init (&guc->hwconfig); +if (ret) +drm_err (&i915->drm,"Failed to retrieve hwconfig table: %d\n" , ret); + ret =guc_enable_communication (guc);if (ret) goto err_log_capture;
@@ -563,6 +567,8 @@ static void __uc_fini_hw(struct intel_uc *uc)if (intel_uc_uses_guc_submission (uc))intel_guc_submission_disable (guc); +intel_guc_hwconfig_fini (&guc->hwconfig); +__uc_sanitize (uc); }
Signature · 1 line
2.25.1
PATCH v3 2/2 drm/i915/uapi: Add query for hwconfig table
In reply to [email protected]From: Rodrigo Vivi <[email protected]>
GuC contains a consolidated table with a bunch of information about the current device.
Previously, this information was spread and hardcoded to all the components including GuC, i915 and various UMDs. The goal here is to consolidate the data into GuC in a way that all interested components can grab the very latest and synchronized information using a simple query.
As per most of the other queries, this one can be called twice. Once with item.length=0 to determine the exact buffer size, then allocate the user memory and call it again for to retrieve the table data. For example:
struct drm_i915_query_item item = {
.query_id = DRM_I915_QUERY_HWCONCFIG_TABLE; };
query.items_ptr = (int64_t) &item;
query.num_items = 1;
ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query));
if (item.length <= 0)
return -ENOENT;
data = malloc(item.length); item.data_ptr = (int64_t) &data; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query));
// Parse the data as appropriate...
The returned array is a simple and flexible KLV (Key/Length/Value) formatted table. For example, it could be just:
enum device_attr {
ATTR_SOME_VALUE = 0,
ATTR_SOME_MASK = 1,
};
static const u32 hwconfig[] = {
ATTR_SOME_VALUE,
1, // Value Length in DWords
8, // Value ATTR_SOME_MASK,
3,
0x00FFFFFFFF, 0xFFFFFFFF, 0xFF000000,};
The attribute ids are defined in a hardware spec.
--- drivers/gpu/drm/i915/i915_query.c | 23 +++++++++++++++++++++++ include/uapi/drm/i915_drm.h | 1 + 2 files changed, 24 insertions(+)
drivers/gpu/drm/i915/i915_query.c +23 -0
@@ -479,12 +479,35 @@ static int query_memregion_info(struct drm_i915_private *i915,return total_length; } +static int query_hwconfig_table (struct drm_i915_private *i915, +struct drm_i915_query_item *query_item) +{ +struct intel_gt *gt =to_gt (i915); +struct intel_guc_hwconfig *hwconfig = >->uc.guc.hwconfig; + +if (!hwconfig->size || !hwconfig->ptr) +return -ENODEV ; + +if (query_item->length ==0 ) +return hwconfig->size; + +if (query_item->length < hwconfig->size) +return -EINVAL ; + +if (copy_to_user (u64_to_user_ptr (query_item->data_ptr), + hwconfig->ptr, hwconfig->size)) +return -EFAULT ; + +return hwconfig->size; +} +static int (*const i915_query_funcs[])(struct drm_i915_private *dev_priv,struct drm_i915_query_item *query_item) = { query_topology_info, query_engine_info, query_perf_config, query_memregion_info, + query_hwconfig_table, };int i915_query_ioctl (struct drm_device *dev,void *data,struct drm_file *file)
include/uapi/drm/i915_drm.h +1 -0
@@ -2685,6 +2685,7 @@ struct drm_i915_query_item {#define DRM_I915_QUERY_ENGINE_INFO 2#define DRM_I915_QUERY_PERF_CONFIG 3#define DRM_I915_QUERY_MEMORY_REGIONS 4 +#define DRM_I915_QUERY_HWCONFIG_TABLE 5/* Must be kept compact -- no holes and well documented */ /**
Signature · 1 line
2.25.1
Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/uapi: Add query for hwconfig table
Quoted 9 lines · [email protected] writes:
From: Rodrigo Vivi <[email protected]>
GuC contains a consolidated table with a bunch of information about the current device.
Previously, this information was spread and hardcoded to all the components including GuC, i915 and various UMDs. The goal here is to consolidate the data into GuC in a way that all interested components can grab the very latest and synchronized information using a simple query.
This "consolidate" goal is not what I was told for the purpose of this. I don't think these paragraphs are the true.
Quoted 33 lines
As per most of the other queries, this one can be called twice. Once with item.length=0 to determine the exact buffer size, then allocate the user memory and call it again for to retrieve the table data. For example:
struct drm_i915_query_item item = { .query_id = DRM_I915_QUERY_HWCONCFIG_TABLE;};
query.items_ptr = (int64_t) &item;
query.num_items = 1;ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query));if (item.length <= 0)
return -ENOENT;data = malloc(item.length); item.data_ptr = (int64_t) &data; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query));// Parse the data as appropriate...
The returned array is a simple and flexible KLV (Key/Length/Value) formatted table. For example, it could be just:
enumdevice_attr{
ATTR_SOME_VALUE= 0,
ATTR_SOME_MASK= 1,
};static const u32 hwconfig[] = { ATTR_SOME_VALUE, 1, // Value Length in DWords 8, // Value
Quoted 4 lines
ATTR_SOME_MASK, 3, 0x00FFFFFFFF, 0xFFFFFFFF, 0xFF000000,};
You said on 03 Nov 2021 that you would remove the parts of this commit message that document the format. Why? Because i915 will not make any guarantees as to the format of what is returned. Thus, i915 should not comment on the format.
Can you Cc me on future postings of this patch?
Quoted 1 line
The attribute ids are defined in a hardware spec.
As this spec is not published, it's hard to verify or refute this claim.
Think this is a more accurate commit message for this patch:
In this interface i915 is returning a currently undocumented blob of data which it receives from the closed source guc software. The format of this blob *might* be defined in a hardware spec in the future.
I'm sure you will prefer to replace "might" with "is planned to". I think "might" is more accurate, but I suppose the other would be acceptable.
-Jordan
Quoted 67 lines
Cc Tvrtko Ursulin <[email protected]>Cc Kenneth Graunke <[email protected]>Cc Michal Wajdeczko <[email protected]>Cc Slawomir Milczarek <[email protected]>Signed-off-by Rodrigo Vivi <[email protected]>Signed-off-by John Harrison <[email protected]>Reviewed-by Matthew Brost <[email protected]>--- drivers/gpu/drm/i915/i915_query.c | 23 +++++++++++++++++++++++ include/uapi/drm/i915_drm.h | 1 + 2 files changed, 24 insertions(+)drivers/gpu/drm/i915/i915_query.c +23
-0@@ -479,12 +479,35 @@ static int query_memregion_info(struct drm_i915_private *i915,return total_length; } +static int query_hwconfig_table (struct drm_i915_private *i915, +struct drm_i915_query_item *query_item) +{ +struct intel_gt *gt =to_gt (i915); +struct intel_guc_hwconfig *hwconfig = >->uc.guc.hwconfig; + +if (!hwconfig->size || !hwconfig->ptr) +return -ENODEV ; + +if (query_item->length ==0 ) +return hwconfig->size; + +if (query_item->length < hwconfig->size) +return -EINVAL ; + +if (copy_to_user (u64_to_user_ptr (query_item->data_ptr), + hwconfig->ptr, hwconfig->size)) +return -EFAULT ; + +return hwconfig->size; +} +static int (*const i915_query_funcs[])(struct drm_i915_private *dev_priv,struct drm_i915_query_item *query_item) = { query_topology_info, query_engine_info, query_perf_config, query_memregion_info, + query_hwconfig_table, };int i915_query_ioctl (struct drm_device *dev,void *data,struct drm_file *file)include/uapi/drm/i915_drm.h +1
-0@@ -2685,6 +2685,7 @@ struct drm_i915_query_item {#define DRM_I915_QUERY_ENGINE_INFO 2#define DRM_I915_QUERY_PERF_CONFIG 3#define DRM_I915_QUERY_MEMORY_REGIONS 4 +#define DRM_I915_QUERY_HWCONFIG_TABLE 5/* Must be kept compact -- no holes and well documented */ /** Signature · 1 line
2.25.1
Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/uapi: Add query for hwconfig table
Quoted 7 lines · Jordan Justen
Quoted 5 lines · [email protected] writes:
From: Rodrigo Vivi <[email protected]>
GuC contains a consolidated table with a bunch of information about the current device.
Quoted 6 lines
Quoted 4 lines
Previously, this information was spread and hardcoded to all the components including GuC, i915 and various UMDs. The goal here is to consolidate the data into GuC in a way that all interested components can grab the very latest and synchronized information using a simple query.
This "consolidate" goal is not what I was told for the purpose of this. I don't think these paragraphs are the true.
The intention is to remove multiple hardcoded tables spread across a bunch of different drivers and replace them with a single table retrieved from the hardware itself. That sounds like consolidation to me.
Quoted 34 lines
Quoted 34 lines
As per most of the other queries, this one can be called twice. Once with item.length=0 to determine the exact buffer size, then allocate the user memory and call it again for to retrieve the table data. For example:
struct drm_i915_query_item item = { .query_id = DRM_I915_QUERY_HWCONCFIG_TABLE; }; query.items_ptr = (int64_t) &item; query.num_items = 1; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query)); if (item.length <= 0) return -ENOENT; data = malloc(item.length); item.data_ptr = (int64_t) &data; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query)); // Parse the data as appropriate...The returned array is a simple and flexible KLV (Key/Length/Value) formatted table. For example, it could be just:
enumdevice_attr{
ATTR_SOME_VALUE= 0,
ATTR_SOME_MASK= 1,
};static const u32 hwconfig[] = { ATTR_SOME_VALUE, 1, // Value Length in DWords 8, // Value
Quoted 8 lines
Quoted 4 lines
ATTR_SOME_MASK, 3, 0x00FFFFFFFF, 0xFFFFFFFF, 0xFF000000,};
You said on 03 Nov 2021 that you would remove the parts of this commit message that document the format. Why? Because i915 will not make any guarantees as to the format of what is returned. Thus, i915 should not comment on the format.
And you replied that you would prefer to keep it.
Quoted 13 lines
Can you Cc me on future postings of this patch?
Quoted 1 line
The attribute ids are defined in a hardware spec.
As this spec is not published, it's hard to verify or refute this claim.
Think this is a more accurate commit message for this patch:
In this interface i915 is returning a currently undocumented blob of data which it receives from the closed source guc software. The format of this blob *might* be defined in a hardware spec in the future.
Quoted 5 lines
I'm sure you will prefer to replace "might" with "is planned to". I think "might" is more accurate, but I suppose the other would be acceptable.
-Jordan
Getting brand new spec documents published is not a fast process. That doesn't mean it isn't going to happen. Also, just because a document is currently confidential and private doesn't mean that it doesn't exist.
John.
Quoted 67 lines
Quoted 67 lines
Cc Tvrtko Ursulin <[email protected]>Cc Kenneth Graunke <[email protected]>Cc Michal Wajdeczko <[email protected]>Cc Slawomir Milczarek <[email protected]>Signed-off-by Rodrigo Vivi <[email protected]>Signed-off-by John Harrison <[email protected]>Reviewed-by Matthew Brost <[email protected]>--- drivers/gpu/drm/i915/i915_query.c | 23 +++++++++++++++++++++++ include/uapi/drm/i915_drm.h | 1 + 2 files changed, 24 insertions(+)drivers/gpu/drm/i915/i915_query.c +23
-0@@ -479,12 +479,35 @@ static int query_memregion_info(struct drm_i915_private *i915,return total_length; } +static int query_hwconfig_table (struct drm_i915_private *i915, +struct drm_i915_query_item *query_item) +{ +struct intel_gt *gt =to_gt (i915); +struct intel_guc_hwconfig *hwconfig = >->uc.guc.hwconfig; + +if (!hwconfig->size || !hwconfig->ptr) +return -ENODEV ; + +if (query_item->length ==0 ) +return hwconfig->size; + +if (query_item->length < hwconfig->size) +return -EINVAL ; + +if (copy_to_user (u64_to_user_ptr (query_item->data_ptr), + hwconfig->ptr, hwconfig->size)) +return -EFAULT ; + +return hwconfig->size; +} +static int (*const i915_query_funcs[])(struct drm_i915_private *dev_priv,struct drm_i915_query_item *query_item) = { query_topology_info, query_engine_info, query_perf_config, query_memregion_info, + query_hwconfig_table, };int i915_query_ioctl (struct drm_device *dev,void *data,struct drm_file *file)include/uapi/drm/i915_drm.h +1
-0@@ -2685,6 +2685,7 @@ struct drm_i915_query_item {#define DRM_I915_QUERY_ENGINE_INFO 2#define DRM_I915_QUERY_PERF_CONFIG 3#define DRM_I915_QUERY_MEMORY_REGIONS 4 +#define DRM_I915_QUERY_HWCONFIG_TABLE 5/* Must be kept compact -- no holes and well documented */ /** Signature · 1 line
2.25.1
Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/uapi: Add query for hwconfig table
Quoted 12 lines · John Harrison
Quoted 11 lines · Jordan Justen
Quoted 9 lines · [email protected] writes:
From: Rodrigo Vivi <[email protected]>
GuC contains a consolidated table with a bunch of information about the current device.
Previously, this information was spread and hardcoded to all the components including GuC, i915 and various UMDs. The goal here is to consolidate the data into GuC in a way that all interested components can grab the very latest and synchronized information using a simple query.
Quoted 5 lines
Quoted 2 lines
This "consolidate" goal is not what I was told for the purpose of this. I don't think these paragraphs are the true.
The intention is to remove multiple hardcoded tables spread across a bunch of different drivers and replace them with a single table retrieved from the hardware itself. That sounds like consolidation to me.
That is not what I was told. That is apparently what someone is trying to sell here.
Mesa would prefer to "hardcode" info rather than depend on the closed source guc software.
Quoted 38 lines
Quoted 38 lines
Quoted 38 lines
As per most of the other queries, this one can be called twice. Once with item.length=0 to determine the exact buffer size, then allocate the user memory and call it again for to retrieve the table data. For example:
struct drm_i915_query_item item = { .query_id = DRM_I915_QUERY_HWCONCFIG_TABLE; }; query.items_ptr = (int64_t) &item; query.num_items = 1; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query)); if (item.length <= 0) return -ENOENT; data = malloc(item.length); item.data_ptr = (int64_t) &data; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query)); // Parse the data as appropriate...The returned array is a simple and flexible KLV (Key/Length/Value) formatted table. For example, it could be just:
enum device_attr { ATTR_SOME_VALUE = 0, ATTR_SOME_MASK = 1, }; static const u32 hwconfig[] = { ATTR_SOME_VALUE, 1, // Value Length in DWords 8, // Value ATTR_SOME_MASK, 3, 0x00FFFFFFFF, 0xFFFFFFFF, 0xFF000000, };
Quoted 5 lines
Quoted 4 lines
You said on 03 Nov 2021 that you would remove the parts of this commit message that document the format. Why? Because i915 will not make any guarantees as to the format of what is returned. Thus, i915 should not comment on the format.
And you replied that you would prefer to keep it.
No, I did not.
You said, "Sure. Can remove comments." to which, I replied, "Obviously not what should be done, but apparently all i915 is willing to do."
So, i915 should document and stand behind this blob's format. But, if they are not willing to, they shouldn't half-heartedly put some text in a commit message.
Quoted 13 lines
Quoted 13 lines
Can you Cc me on future postings of this patch?
Quoted 1 line
The attribute ids are defined in a hardware spec.
As this spec is not published, it's hard to verify or refute this claim.
Think this is a more accurate commit message for this patch:
In this interface i915 is returning a currently undocumented blob of data which it receives from the closed source guc software. The format of this blob *might* be defined in a hardware spec in the future.
Quoted 6 lines
Quoted 5 lines
I'm sure you will prefer to replace "might" with "is planned to". I think "might" is more accurate, but I suppose the other would be acceptable.
-Jordan
Getting brand new spec documents published is not a fast process.
Heh.
Have you learned anything new about the status of it in the past 3 months?
Quoted 1 line
That doesn't mean it isn't going to happen.
It also doesn't mean it is going to happen either. Maybe you want to add some text wherein Intel guarantees that it will be released in a spec by some date?
Quoted 2 lines
Also, just because a document is currently confidential and private doesn't mean that it doesn't exist.
Should we add "This is documented in a private spec, so it really does exist!"?
-Jordan
Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/uapi: Add query for hwconfig table
In reply to [email protected]John, Rodrigo,
It is now clear to me just how dependent i915 is going to be on the closed source guc software, and that's just a fact of life for our graphics stack going forward.
In that context, it seems kind of pointless for me to make a big deal out of this peripheral "query item" commit message. I still think something as simple and to the point as:
"In this interface i915 is returning a blob of data which it receives from the guc software. This blob provides some useful data about the hardware for drivers. The format of this blob will be documented in the Programmer Reference Manuals when released."
... would be better, but obviously this is really just down in the noise in terms of concerns about the greater issue. So, feel free (to continue) to ignore my suggestion.
Sorry for having wasted your time,
-Jordan
Quoted 116 lines · [email protected] writes:
From: Rodrigo Vivi <[email protected]>
GuC contains a consolidated table with a bunch of information about the current device.
Previously, this information was spread and hardcoded to all the components including GuC, i915 and various UMDs. The goal here is to consolidate the data into GuC in a way that all interested components can grab the very latest and synchronized information using a simple query.
As per most of the other queries, this one can be called twice. Once with item.length=0 to determine the exact buffer size, then allocate the user memory and call it again for to retrieve the table data. For example:
struct drm_i915_query_item item = { .query_id = DRM_I915_QUERY_HWCONCFIG_TABLE;};
query.items_ptr = (int64_t) &item;
query.num_items = 1;ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query));if (item.length <= 0)
return -ENOENT;data = malloc(item.length); item.data_ptr = (int64_t) &data; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query));// Parse the data as appropriate...
The returned array is a simple and flexible KLV (Key/Length/Value) formatted table. For example, it could be just:
enumdevice_attr{
ATTR_SOME_VALUE= 0,
ATTR_SOME_MASK= 1,
};static const u32 hwconfig[] = { ATTR_SOME_VALUE, 1, // Value Length in DWords 8, // ValueATTR_SOME_MASK, 3, 0x00FFFFFFFF, 0xFFFFFFFF, 0xFF000000,};
The attribute ids are defined in a hardware spec.
Cc Tvrtko Ursulin <[email protected]>Cc Kenneth Graunke <[email protected]>Cc Michal Wajdeczko <[email protected]>Cc Slawomir Milczarek <[email protected]>Signed-off-by Rodrigo Vivi <[email protected]>Signed-off-by John Harrison <[email protected]>Reviewed-by Matthew Brost <[email protected]>--- drivers/gpu/drm/i915/i915_query.c | 23 +++++++++++++++++++++++ include/uapi/drm/i915_drm.h | 1 + 2 files changed, 24 insertions(+)drivers/gpu/drm/i915/i915_query.c +23
-0@@ -479,12 +479,35 @@ static int query_memregion_info(struct drm_i915_private *i915,return total_length; } +static int query_hwconfig_table (struct drm_i915_private *i915, +struct drm_i915_query_item *query_item) +{ +struct intel_gt *gt =to_gt (i915); +struct intel_guc_hwconfig *hwconfig = >->uc.guc.hwconfig; + +if (!hwconfig->size || !hwconfig->ptr) +return -ENODEV ; + +if (query_item->length ==0 ) +return hwconfig->size; + +if (query_item->length < hwconfig->size) +return -EINVAL ; + +if (copy_to_user (u64_to_user_ptr (query_item->data_ptr), + hwconfig->ptr, hwconfig->size)) +return -EFAULT ; + +return hwconfig->size; +} +static int (*const i915_query_funcs[])(struct drm_i915_private *dev_priv,struct drm_i915_query_item *query_item) = { query_topology_info, query_engine_info, query_perf_config, query_memregion_info, + query_hwconfig_table, };int i915_query_ioctl (struct drm_device *dev,void *data,struct drm_file *file)include/uapi/drm/i915_drm.h +1
-0@@ -2685,6 +2685,7 @@ struct drm_i915_query_item {#define DRM_I915_QUERY_ENGINE_INFO 2#define DRM_I915_QUERY_PERF_CONFIG 3#define DRM_I915_QUERY_MEMORY_REGIONS 4 +#define DRM_I915_QUERY_HWCONFIG_TABLE 5/* Must be kept compact -- no holes and well documented */ /** Signature · 1 line
2.25.1
Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/uapi: Add query for hwconfig table
Quoted 6 lines · Jordan Justen
John, Rodrigo,
It is now clear to me just how dependent i915 is going to be on the closed source guc software, and that's just a fact of life for our graphics stack going forward.
Quoted 8 lines
In that context, it seems kind of pointless for me to make a big deal out of this peripheral "query item" commit message. I still think something as simple and to the point as:
"In this interface i915 is returning a blob of data which it receives from the guc software. This blob provides some useful data about the hardware for drivers. The format of this blob will be documented in the Programmer Reference Manuals when released."
As I said on the internal email thread, *if you use my commit message suggestion*, then, begrudgingly, you can add my:
to the patch.
Regardless of the commit message, I think you can add:
In truth, I've only tested this via the "prelim" i915 Linux uapi fork on an internal kernel tree, but I think that probably is close enough.
In case you find it helpful, maybe:
Ref: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14511
-Jordan
Quoted 127 lines
... would be better, but obviously this is really just down in the noise in terms of concerns about the greater issue. So, feel free (to continue) to ignore my suggestion.
Sorry for having wasted your time,
-Jordan
Quoted 116 lines · [email protected] writes:
From: Rodrigo Vivi <[email protected]>
GuC contains a consolidated table with a bunch of information about the current device.
Previously, this information was spread and hardcoded to all the components including GuC, i915 and various UMDs. The goal here is to consolidate the data into GuC in a way that all interested components can grab the very latest and synchronized information using a simple query.
As per most of the other queries, this one can be called twice. Once with item.length=0 to determine the exact buffer size, then allocate the user memory and call it again for to retrieve the table data. For example:
struct drm_i915_query_item item = { .query_id = DRM_I915_QUERY_HWCONCFIG_TABLE;};
query.items_ptr = (int64_t) &item;
query.num_items = 1;ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query));if (item.length <= 0)
return -ENOENT;data = malloc(item.length); item.data_ptr = (int64_t) &data; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query));// Parse the data as appropriate...
The returned array is a simple and flexible KLV (Key/Length/Value) formatted table. For example, it could be just:
enumdevice_attr{
ATTR_SOME_VALUE= 0,
ATTR_SOME_MASK= 1,
};static const u32 hwconfig[] = { ATTR_SOME_VALUE, 1, // Value Length in DWords 8, // ValueATTR_SOME_MASK, 3, 0x00FFFFFFFF, 0xFFFFFFFF, 0xFF000000,};
The attribute ids are defined in a hardware spec.
Cc Tvrtko Ursulin <[email protected]>Cc Kenneth Graunke <[email protected]>Cc Michal Wajdeczko <[email protected]>Cc Slawomir Milczarek <[email protected]>Signed-off-by Rodrigo Vivi <[email protected]>Signed-off-by John Harrison <[email protected]>Reviewed-by Matthew Brost <[email protected]>--- drivers/gpu/drm/i915/i915_query.c | 23 +++++++++++++++++++++++ include/uapi/drm/i915_drm.h | 1 + 2 files changed, 24 insertions(+)drivers/gpu/drm/i915/i915_query.c +23
-0@@ -479,12 +479,35 @@ static int query_memregion_info(struct drm_i915_private *i915,return total_length; } +static int query_hwconfig_table (struct drm_i915_private *i915, +struct drm_i915_query_item *query_item) +{ +struct intel_gt *gt =to_gt (i915); +struct intel_guc_hwconfig *hwconfig = >->uc.guc.hwconfig; + +if (!hwconfig->size || !hwconfig->ptr) +return -ENODEV ; + +if (query_item->length ==0 ) +return hwconfig->size; + +if (query_item->length < hwconfig->size) +return -EINVAL ; + +if (copy_to_user (u64_to_user_ptr (query_item->data_ptr), + hwconfig->ptr, hwconfig->size)) +return -EFAULT ; + +return hwconfig->size; +} +static int (*const i915_query_funcs[])(struct drm_i915_private *dev_priv,struct drm_i915_query_item *query_item) = { query_topology_info, query_engine_info, query_perf_config, query_memregion_info, + query_hwconfig_table, };int i915_query_ioctl (struct drm_device *dev,void *data,struct drm_file *file)include/uapi/drm/i915_drm.h +1
-0@@ -2685,6 +2685,7 @@ struct drm_i915_query_item {#define DRM_I915_QUERY_ENGINE_INFO 2#define DRM_I915_QUERY_PERF_CONFIG 3#define DRM_I915_QUERY_MEMORY_REGIONS 4 +#define DRM_I915_QUERY_HWCONFIG_TABLE 5/* Must be kept compact -- no holes and well documented */ /** Signature · 1 line
2.25.1
Re: [PATCH v3 2/2] drm/i915/uapi: Add query for hwconfig table
In reply to [email protected]Quoted 108 lines · On Wed, Jan 19, 2022 at 9:35 PM <[email protected]> wrote:
From: Rodrigo Vivi <[email protected]>
GuC contains a consolidated table with a bunch of information about the current device.
Previously, this information was spread and hardcoded to all the components including GuC, i915 and various UMDs. The goal here is to consolidate the data into GuC in a way that all interested components can grab the very latest and synchronized information using a simple query.
As per most of the other queries, this one can be called twice. Once with item.length=0 to determine the exact buffer size, then allocate the user memory and call it again for to retrieve the table data. For example:
struct drm_i915_query_item item = { .query_id = DRM_I915_QUERY_HWCONCFIG_TABLE;};
query.items_ptr = (int64_t) &item;
query.num_items = 1;ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query));if (item.length <= 0)
return -ENOENT;data = malloc(item.length); item.data_ptr = (int64_t) &data; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query));// Parse the data as appropriate...
The returned array is a simple and flexible KLV (Key/Length/Value) formatted table. For example, it could be just:
enumdevice_attr{
ATTR_SOME_VALUE= 0,
ATTR_SOME_MASK= 1,
};static const u32 hwconfig[] = { ATTR_SOME_VALUE, 1, // Value Length in DWords 8, // ValueATTR_SOME_MASK, 3, 0x00FFFFFFFF, 0xFFFFFFFF, 0xFF000000,};
The attribute ids are defined in a hardware spec.
Cc Tvrtko Ursulin <[email protected]>Cc Kenneth Graunke <[email protected]>Cc Michal Wajdeczko <[email protected]>Cc Slawomir Milczarek <[email protected]>Signed-off-by Rodrigo Vivi <[email protected]>Signed-off-by John Harrison <[email protected]>Reviewed-by Matthew Brost <[email protected]>--- drivers/gpu/drm/i915/i915_query.c | 23 +++++++++++++++++++++++ include/uapi/drm/i915_drm.h | 1 + 2 files changed, 24 insertions(+)drivers/gpu/drm/i915/i915_query.c +23
-0@@ -479,12 +479,35 @@ static int query_memregion_info(struct drm_i915_private *i915,return total_length; } +static int query_hwconfig_table (struct drm_i915_private *i915, +struct drm_i915_query_item *query_item) +{ +struct intel_gt *gt =to_gt (i915); +struct intel_guc_hwconfig *hwconfig = >->uc.guc.hwconfig; + +if (!hwconfig->size || !hwconfig->ptr) +return -ENODEV ; + +if (query_item->length ==0 ) +return hwconfig->size; + +if (query_item->length < hwconfig->size) +return -EINVAL ; + +if (copy_to_user (u64_to_user_ptr (query_item->data_ptr), + hwconfig->ptr, hwconfig->size)) +return -EFAULT ; + +return hwconfig->size; +} +static int (*const i915_query_funcs[])(struct drm_i915_private *dev_priv,struct drm_i915_query_item *query_item) = { query_topology_info, query_engine_info, query_perf_config, query_memregion_info, + query_hwconfig_table, };int i915_query_ioctl (struct drm_device *dev,void *data,struct drm_file *file)include/uapi/drm/i915_drm.h +0
-0
include/uapi/drm/i915_drm.h struct drm_i915_query_item { · line 2689
Quoted 5 lines
include/uapi/drm/i915_drm.h +1
-0@@ -2685,6 +2685,7 @@ struct drm_i915_query_item {#define DRM_I915_QUERY_ENGINE_INFO 2#define DRM_I915_QUERY_PERF_CONFIG 3#define DRM_I915_QUERY_MEMORY_REGIONS 4 +#define DRM_I915_QUERY_HWCONFIG_TABLE 5/* Must be kept compact -- no holes and well documented */
New uapi needs kerneldoc in the uapi header, and please fill in any gaps you have (i.e. if the query uapi this is built on top of isn't fully documented yet).
Also this holds across the board, so please keep in mind in patch review. -Daniel
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Re: [PATCH v3 2/2] drm/i915/uapi: Add query for hwconfig table
Quoted 117 lines · Daniel Vetter
Quoted 107 lines · On Wed, Jan 19, 2022 at 9:35 PM <[email protected]> wrote:
From: Rodrigo Vivi <[email protected]>
GuC contains a consolidated table with a bunch of information about the current device.
Previously, this information was spread and hardcoded to all the components including GuC, i915 and various UMDs. The goal here is to consolidate the data into GuC in a way that all interested components can grab the very latest and synchronized information using a simple query.
As per most of the other queries, this one can be called twice. Once with item.length=0 to determine the exact buffer size, then allocate the user memory and call it again for to retrieve the table data. For example:
struct drm_i915_query_item item = { .query_id = DRM_I915_QUERY_HWCONCFIG_TABLE; }; query.items_ptr = (int64_t) &item; query.num_items = 1; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query)); if (item.length <= 0) return -ENOENT; data = malloc(item.length); item.data_ptr = (int64_t) &data; ioctl(fd, DRM_IOCTL_I915_QUERY, query, sizeof(query)); // Parse the data as appropriate...The returned array is a simple and flexible KLV (Key/Length/Value) formatted table. For example, it could be just:
enum device_attr { ATTR_SOME_VALUE = 0, ATTR_SOME_MASK = 1, }; static const u32 hwconfig[] = { ATTR_SOME_VALUE, 1, // Value Length in DWords 8, // Value ATTR_SOME_MASK, 3, 0x00FFFFFFFF, 0xFFFFFFFF, 0xFF000000, };The attribute ids are defined in a hardware spec.
Cc Tvrtko Ursulin <[email protected]>Cc Kenneth Graunke <[email protected]>Cc Michal Wajdeczko <[email protected]>Cc Slawomir Milczarek <[email protected]>Signed-off-by Rodrigo Vivi <[email protected]>Signed-off-by John Harrison <[email protected]>Reviewed-by Matthew Brost <[email protected]>--- drivers/gpu/drm/i915/i915_query.c | 23 +++++++++++++++++++++++ include/uapi/drm/i915_drm.h | 1 + 2 files changed, 24 insertions(+)drivers/gpu/drm/i915/i915_query.c +23
-0@@ -479,12 +479,35 @@ static int query_memregion_info(struct drm_i915_private *i915,return total_length; } +static int query_hwconfig_table (struct drm_i915_private *i915, +struct drm_i915_query_item *query_item) +{ +struct intel_gt *gt =to_gt (i915); +struct intel_guc_hwconfig *hwconfig = >->uc.guc.hwconfig; + +if (!hwconfig->size || !hwconfig->ptr) +return -ENODEV ; + +if (query_item->length ==0 ) +return hwconfig->size; + +if (query_item->length < hwconfig->size) +return -EINVAL ; + +if (copy_to_user (u64_to_user_ptr (query_item->data_ptr), + hwconfig->ptr, hwconfig->size)) +return -EFAULT ; + +return hwconfig->size; +} +static int (*const i915_query_funcs[])(struct drm_i915_private *dev_priv,struct drm_i915_query_item *query_item) = { query_topology_info, query_engine_info, query_perf_config, query_memregion_info, + query_hwconfig_table, };int i915_query_ioctl (struct drm_device *dev,void *data,struct drm_file *file)include/uapi/drm/i915_drm.h +0
-0include/uapi/drm/i915_drm.h struct drm_i915_query_item { · line 2689
Quoted 5 lines
include/uapi/drm/i915_drm.h +1
-0@@ -2685,6 +2685,7 @@ struct drm_i915_query_item {#define DRM_I915_QUERY_ENGINE_INFO 2#define DRM_I915_QUERY_PERF_CONFIG 3#define DRM_I915_QUERY_MEMORY_REGIONS 4 +#define DRM_I915_QUERY_HWCONFIG_TABLE 5/* Must be kept compact -- no holes and well documented */ New uapi needs kerneldoc in the uapi header, and please fill in any gaps you have (i.e. if the query uapi this is built on top of isn't fully documented yet).
Quoted 2 lines
Also this holds across the board, so please keep in mind in patch review. -Daniel
There is no extra documentation to add.
The query interface itself is already documented. This new query does not have any kernel defined data structures associated with it. There is just 'struct drm_i915_query_item' with a length and a pointer, all of which are fully documented.
John.
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add support for querying hw info that UMDs need
In reply to [email protected]== Series Details ==
== Series Details ==
Series: Add support for querying hw info that UMDs need
URL : https://patchwork.freedesktop.org/series/99060/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 59215be8fef3 drm/i915/guc: Add fetch of hwconfig table -:78: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #78: new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 227 lines checked 236332f9458a drm/i915/uapi: Add query for hwconfig table
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Add support for querying hw info that UMDs need
In reply to [email protected]== Series Details ==
== Series Details ==
Series: Add support for querying hw info that UMDs need
URL : https://patchwork.freedesktop.org/series/99060/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for Add support for querying hw info that UMDs need
In reply to [email protected]== Series Details ==
== Series Details ==
Series: Add support for querying hw info that UMDs need
URL : https://patchwork.freedesktop.org/series/99060/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11110 -> Patchwork_22027
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/index.html
Participating hosts (45 -> 42)
------------------------------
Missing (3): fi-bsw-cyan bat-jsl-2 fi-bdw-samus
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_22027:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@i915_hangman@error-state-basic:
- {bat-adlp-6}: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/bat-adlp-6/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/bat-adlp-6/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_22027 that come from known issues:
### CI changes ###
#### Issues hit ####
* boot:
- fi-ilk-650: [PASS][3] -> [FAIL][4] ([i915#4684])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/fi-ilk-650/boot.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/fi-ilk-650/boot.html
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@semaphore:
- fi-bdw-5557u: NOTRUN -> [SKIP][5] ([fdo#109271]) +31 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/fi-bdw-5557u/igt@amdgpu/[email protected]
* igt@amdgpu/amd_cs_nop@sync-fork-gfx0:
- fi-skl-6600u: NOTRUN -> [SKIP][6] ([fdo#109271]) +17 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/fi-skl-6600u/igt@amdgpu/[email protected]
* igt@i915_selftest@live@hangcheck:
- bat-dg1-5: [PASS][7] -> [DMESG-FAIL][8] ([i915#4494])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/bat-dg1-5/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/bat-dg1-5/igt@i915_selftest@[email protected]
- bat-dg1-6: [PASS][9] -> [DMESG-FAIL][10] ([i915#4494])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/bat-dg1-6/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/bat-dg1-6/igt@i915_selftest@[email protected]
- fi-snb-2600: [PASS][11] -> [INCOMPLETE][12] ([i915#3921])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/fi-snb-2600/igt@i915_selftest@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/fi-snb-2600/igt@i915_selftest@[email protected]
* igt@kms_chamelium@dp-crc-fast:
- fi-bdw-5557u: NOTRUN -> [SKIP][13] ([fdo#109271] / [fdo#111827]) +8 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/fi-bdw-5557u/igt@[email protected]
#### Possible fixes ####
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [DMESG-WARN][14] ([i915#4269]) -> [PASS][15]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/fi-cml-u2/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/fi-cml-u2/igt@[email protected]
#### Warnings ####
* igt@i915_pm_rpm@basic-rte:
- fi-kbl-guc: [SKIP][16] ([fdo#109271]) -> [FAIL][17] ([i915#579])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/fi-kbl-guc/igt@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/fi-kbl-guc/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
[i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
[i915#4684]: https://gitlab.freedesktop.org/drm/intel/issues/4684
[i915#579]: https://gitlab.freedesktop.org/drm/intel/issues/579
Build changes
-------------
* IGT: IGT_6329 -> IGTPW_6562
* Linux: CI_DRM_11110 -> Patchwork_22027
CI-20190529: 20190529
CI_DRM_11110: 773fc0fe92f90fa7bbbcdccffa7436259bbab22f @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_6562: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6562/index.html
IGT_6329: 38f656fdd61119105ecfa2c4dac157cd7dcad204 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_22027: 236332f9458a43aad7230487dbb6e5e24b76747c @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
236332f9458a drm/i915/uapi: Add query for hwconfig table 59215be8fef3 drm/i915/guc: Add fetch of hwconfig table
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for Add support for querying hw info that UMDs need
In reply to [email protected]== Series Details ==
== Series Details ==
Series: Add support for querying hw info that UMDs need
URL : https://patchwork.freedesktop.org/series/99060/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11110_full -> Patchwork_22027_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_22027_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_22027_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_22027_full:
### IGT changes ###
#### Possible regressions ####
* {igt@i915_query@hwconfig_table} (NEW):
- shard-tglb: NOTRUN -> [SKIP][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb6/igt@i915_query@hwconfig_table.html
- shard-iclb: NOTRUN -> [SKIP][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb4/igt@i915_query@hwconfig_table.html
* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip:
- shard-tglb: [PASS][3] -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-tglb8/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb7/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip.html
New tests
---------
New tests have been introduced between CI_DRM_11110_full and Patchwork_22027_full:
### New IGT tests (1) ###
* igt@i915_query@hwconfig_table:
- Statuses : 7 skip(s)
- Exec time: [0.0] s
Known issues
------------
Here are the changes found in Patchwork_22027_full that come from known issues:
### CI changes ###
#### Issues hit ####
* boot:
- shard-glk: ([PASS][5], [PASS][6], [PASS][7], [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13], [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25], [PASS][26], [PASS][27], [PASS][28], [PASS][29]) -> ([PASS][30], [PASS][31], [PASS][32], [PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37], [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [FAIL][43], [PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], [PASS][49], [PASS][50], [PASS][51], [PASS][52], [PASS][53], [PASS][54]) ([i915#4392])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk9/boot.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk9/boot.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk8/boot.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk8/boot.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk8/boot.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk7/boot.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk7/boot.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk7/boot.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk6/boot.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk6/boot.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk6/boot.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk5/boot.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk5/boot.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk5/boot.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk4/boot.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk4/boot.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk3/boot.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk3/boot.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk3/boot.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk2/boot.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk2/boot.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk2/boot.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk1/boot.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk1/boot.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk1/boot.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk3/boot.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk9/boot.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk7/boot.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk8/boot.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk8/boot.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk9/boot.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk9/boot.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk1/boot.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk1/boot.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk1/boot.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk2/boot.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk2/boot.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk2/boot.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk2/boot.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk3/boot.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk3/boot.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk4/boot.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk4/boot.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk4/boot.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk5/boot.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk5/boot.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk5/boot.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/boot.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/boot.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/boot.html
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@process:
- shard-snb: NOTRUN -> [SKIP][55] ([fdo#109271] / [i915#1099]) +2 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-snb6/igt@[email protected]
* igt@gem_eio@in-flight-contexts-10ms:
- shard-tglb: [PASS][56] -> [TIMEOUT][57] ([i915#3063])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-tglb6/igt@[email protected]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb8/igt@[email protected]
* igt@gem_eio@unwedge-stress:
- shard-iclb: [PASS][58] -> [TIMEOUT][59] ([i915#2481] / [i915#3070])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-iclb1/igt@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb5/igt@[email protected]
* igt@gem_exec_balancer@parallel-out-fence:
- shard-iclb: [PASS][60] -> [SKIP][61] ([i915#4525]) +1 similar issue
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-iclb4/igt@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb6/igt@[email protected]
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-iclb: [PASS][62] -> [FAIL][63] ([i915#2842])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-iclb8/igt@gem_exec_fair@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb4/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@vcs1:
- shard-iclb: NOTRUN -> [FAIL][64] ([i915#2842])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb1/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][65] -> [FAIL][66] ([i915#2842])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-tglb5/igt@gem_exec_fair@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-apl: NOTRUN -> [FAIL][67] ([i915#2842])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl4/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [PASS][68] -> [FAIL][69] ([i915#2842])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk5/igt@gem_exec_fair@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/igt@gem_exec_fair@[email protected]
* igt@gem_exec_params@secure-non-root:
- shard-tglb: NOTRUN -> [SKIP][70] ([fdo#112283])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb6/igt@[email protected]
* igt@gem_exec_whisper@basic-contexts-forked-all:
- shard-glk: [PASS][71] -> [DMESG-WARN][72] ([i915#118])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk3/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk4/igt@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-skl: NOTRUN -> [SKIP][73] ([fdo#109271] / [i915#2190])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl4/igt@[email protected]
* igt@gem_lmem_swapping@heavy-random:
- shard-kbl: NOTRUN -> [SKIP][74] ([fdo#109271] / [i915#4613]) +1 similar issue
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl7/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random:
- shard-skl: NOTRUN -> [SKIP][75] ([fdo#109271] / [i915#4613])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl2/igt@[email protected]
* igt@gem_pxp@reject-modify-context-protection-off-3:
- shard-iclb: NOTRUN -> [SKIP][76] ([i915#4270])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb2/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][77] ([i915#4270])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb2/igt@[email protected]
* igt@gem_render_copy@y-tiled-ccs-to-y-tiled-mc-ccs:
- shard-iclb: NOTRUN -> [SKIP][78] ([i915#768])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb4/igt@[email protected]
* igt@gem_softpin@allocator-evict-all-engines:
- shard-glk: [PASS][79] -> [FAIL][80] ([i915#4171])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk7/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk2/igt@[email protected]
* igt@gem_userptr_blits@dmabuf-sync:
- shard-skl: NOTRUN -> [SKIP][81] ([fdo#109271] / [i915#3323])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl8/igt@[email protected]
* igt@gem_workarounds@suspend-resume-context:
- shard-kbl: [PASS][82] -> [DMESG-WARN][83] ([i915#180])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-kbl3/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl7/igt@[email protected]
* igt@gen9_exec_parse@secure-batches:
- shard-iclb: NOTRUN -> [SKIP][84] ([i915#2856])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb3/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][85] ([i915#2527] / [i915#2856]) +1 similar issue
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb2/igt@[email protected]
* igt@i915_pm_dc@dc6-dpms:
- shard-skl: NOTRUN -> [FAIL][86] ([i915#454])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl3/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: NOTRUN -> [FAIL][87] ([i915#454])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb4/igt@[email protected]
- shard-tglb: NOTRUN -> [FAIL][88] ([i915#454])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb6/igt@[email protected]
* igt@i915_query@query-topology-unsupported:
- shard-iclb: NOTRUN -> [SKIP][89] ([fdo#109302])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb1/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][90] ([fdo#109302])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@[email protected]
* igt@kms_big_fb@linear-8bpp-rotate-90:
- shard-glk: NOTRUN -> [SKIP][91] ([fdo#109271]) +36 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk7/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][92] ([fdo#111614]) +1 similar issue
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-async-flip:
- shard-skl: NOTRUN -> [FAIL][93] ([i915#3743]) +1 similar issue
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl10/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip:
- shard-apl: NOTRUN -> [SKIP][94] ([fdo#109271] / [i915#3777])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl4/igt@[email protected]
* igt@kms_big_fb@y-tiled-64bpp-rotate-90:
- shard-iclb: NOTRUN -> [SKIP][95] ([fdo#110725] / [fdo#111614]) +1 similar issue
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb8/igt@[email protected]
* igt@kms_big_fb@yf-tiled-8bpp-rotate-180:
- shard-tglb: NOTRUN -> [SKIP][96] ([fdo#111615]) +1 similar issue
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb8/igt@[email protected]
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-skl: NOTRUN -> [SKIP][97] ([fdo#109271] / [i915#3777]) +2 similar issues
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl10/igt@[email protected]
* igt@kms_busy@extended-modeset-hang-newfb:
- shard-skl: NOTRUN -> [SKIP][98] ([fdo#109271]) +173 similar issues
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl2/igt@[email protected]
* igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][99] ([fdo#109271] / [i915#3886]) +5 similar issues
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl6/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html
- shard-glk: NOTRUN -> [SKIP][100] ([fdo#109271] / [i915#3886]) +1 similar issue
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][101] ([fdo#109278] / [i915#3886]) +3 similar issues
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb3/igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-crc-primary-basic-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][102] ([fdo#111615] / [i915#3689]) +2 similar issues
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb2/igt@kms_ccs@pipe-b-crc-primary-basic-yf_tiled_ccs.html
* igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs:
- shard-kbl: NOTRUN -> [SKIP][103] ([fdo#109271] / [i915#3886]) +6 similar issues
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl7/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][104] ([fdo#109271] / [i915#3886]) +8 similar issues
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl4/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][105] ([i915#3689])
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb3/igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_ccs.html
* igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][106] ([i915#3689] / [i915#3886]) +4 similar issues
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_color@pipe-b-ctm-negative:
- shard-skl: NOTRUN -> [DMESG-WARN][107] ([i915#1982])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl4/igt@[email protected]
* igt@kms_color@pipe-d-ctm-blue-to-red:
- shard-iclb: NOTRUN -> [SKIP][108] ([fdo#109278] / [i915#1149])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb2/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-0-25:
- shard-snb: NOTRUN -> [SKIP][109] ([fdo#109271] / [fdo#111827]) +3 similar issues
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-snb5/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
- shard-kbl: NOTRUN -> [SKIP][110] ([fdo#109271] / [fdo#111827]) +10 similar issues
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl1/igt@[email protected]
* igt@kms_color_chamelium@pipe-c-ctm-0-25:
- shard-apl: NOTRUN -> [SKIP][111] ([fdo#109271] / [fdo#111827]) +5 similar issues
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl1/igt@[email protected]
* igt@kms_color_chamelium@pipe-c-ctm-max:
- shard-iclb: NOTRUN -> [SKIP][112] ([fdo#109284] / [fdo#111827]) +2 similar issues
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb2/igt@[email protected]
* igt@kms_color_chamelium@pipe-d-degamma:
- shard-glk: NOTRUN -> [SKIP][113] ([fdo#109271] / [fdo#111827]) +3 similar issues
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/igt@[email protected]
- shard-skl: NOTRUN -> [SKIP][114] ([fdo#109271] / [fdo#111827]) +16 similar issues
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl3/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][115] ([fdo#109284] / [fdo#111827]) +6 similar issues
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][116] ([fdo#109278] / [fdo#109284] / [fdo#111827])
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb1/igt@[email protected]
* igt@kms_content_protection@atomic:
- shard-kbl: NOTRUN -> [TIMEOUT][117] ([i915#1319])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl7/igt@[email protected]
* igt@kms_content_protection@uevent:
- shard-kbl: NOTRUN -> [FAIL][118] ([i915#2105])
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl1/igt@[email protected]
- shard-apl: NOTRUN -> [FAIL][119] ([i915#2105])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl4/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-512x512-random:
- shard-iclb: NOTRUN -> [SKIP][120] ([fdo#109278] / [fdo#109279])
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb1/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-max-size-offscreen:
- shard-tglb: NOTRUN -> [SKIP][121] ([i915#3359]) +1 similar issue
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-skl: [PASS][122] -> [SKIP][123] ([fdo#109271]) +15 similar issues
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-skl6/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl2/igt@[email protected]
* igt@kms_cursor_crc@pipe-d-cursor-512x512-onscreen:
- shard-tglb: NOTRUN -> [SKIP][124] ([fdo#109279] / [i915#3359]) +1 similar issue
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb2/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge:
- shard-snb: NOTRUN -> [SKIP][125] ([fdo#109271]) +81 similar issues
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-snb6/igt@[email protected]
* igt@kms_cursor_legacy@cursorb-vs-flipa-atomic:
- shard-iclb: NOTRUN -> [SKIP][126] ([fdo#109274] / [fdo#109278])
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb3/igt@[email protected]
* igt@kms_cursor_legacy@cursorb-vs-flipb-atomic:
- shard-tglb: NOTRUN -> [SKIP][127] ([fdo#109274] / [fdo#111825]) +2 similar issues
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-iclb: NOTRUN -> [FAIL][128] ([i915#2346])
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@pipe-d-single-move:
- shard-iclb: NOTRUN -> [SKIP][129] ([fdo#109278]) +11 similar issues
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb3/igt@[email protected]
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-kbl: [PASS][130] -> [INCOMPLETE][131] ([i915#180] / [i915#636])
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-kbl3/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl4/igt@[email protected]
* igt@kms_flip@2x-plain-flip-fb-recreate:
- shard-iclb: NOTRUN -> [SKIP][132] ([fdo#109274])
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb1/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@b-edp1:
- shard-skl: [PASS][133] -> [FAIL][134] ([i915#79])
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-skl8/igt@kms_flip@[email protected]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl1/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: [PASS][135] -> [INCOMPLETE][136] ([i915#636])
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-kbl1/igt@kms_flip@[email protected]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl3/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling:
- shard-iclb: NOTRUN -> [SKIP][137] ([i915#2587])
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb6/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-indfb-draw-mmap-cpu:
- shard-iclb: NOTRUN -> [SKIP][138] ([fdo#109280]) +9 similar issues
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb6/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-indfb-draw-mmap-cpu.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-render:
- shard-tglb: NOTRUN -> [SKIP][139] ([fdo#109280] / [fdo#111825]) +12 similar issues
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb6/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc:
- shard-kbl: NOTRUN -> [SKIP][140] ([fdo#109271]) +146 similar issues
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl6/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [PASS][141] -> [FAIL][142] ([i915#1188])
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-skl8/igt@[email protected]
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl10/igt@[email protected]
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-d-frame-sequence:
- shard-skl: NOTRUN -> [SKIP][143] ([fdo#109271] / [i915#533])
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl6/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes:
- shard-apl: [PASS][144] -> [DMESG-WARN][145] ([i915#180]) +4 similar issues
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-apl7/igt@kms_plane@[email protected]
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl3/igt@kms_plane@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes:
- shard-kbl: NOTRUN -> [DMESG-WARN][146] ([i915#180]) +1 similar issue
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl6/igt@kms_plane@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-skl: NOTRUN -> [FAIL][147] ([i915#265])
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl1/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][148] ([i915#265])
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][149] ([fdo#108145] / [i915#265])
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-alpha-basic:
- shard-skl: NOTRUN -> [FAIL][150] ([fdo#108145] / [i915#265]) +2 similar issues
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl10/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
- shard-kbl: NOTRUN -> [FAIL][151] ([i915#265])
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [PASS][152] -> [FAIL][153] ([fdo#108145] / [i915#265]) +1 similar issue
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-skl8/igt@[email protected]
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl7/igt@[email protected]
* igt@kms_plane_lowres@pipe-a-tiling-y:
- shard-glk: [PASS][154] -> [DMESG-FAIL][155] ([i915#118] / [i915#1888])
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk8/igt@[email protected]
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk3
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/index.html
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Add support for querying hw info that UMDs need
Quoted 39 lines · Patchwork
Project List - Patchwork *Patch Details*
*Series:* Add support for querying hw info that UMDs need
*URL:* https://patchwork.freedesktop.org/series/99060/
*State:* failure
*Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/index.htmlCI Bug Log - changes from
CI_DRM_11110_full->Patchwork_22027_fullSummary
*FAILURE*
Serious unknown changes coming with
Patchwork_22027_fullabsolutely need to be verified manually.If you think the reported changes have nothing to do with the changes introduced in
Patchwork_22027_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.Participating hosts (10 -> 10)No changes in participating hosts
Possible new issues
Here are the unknown changes that may have been introduced in
Patchwork_22027_full:IGT changes
Possible regressions
*
Quoted 12 lines
{igt@i915_query@hwconfig_table} (NEW):
o
shard-tglb: NOTRUN -> SKIP
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb6/igt@i915_query@hwconfig_table.html>
o
shard-iclb: NOTRUN -> SKIP
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb4/igt@i915_query@hwconfig_table.html>Expected. The table only exists on ALD-P and later. So TGL/ICL will be skips.
Quoted 12 lines
*
o*
igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip: o shard-tglb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-tglb8/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip.html> -> INCOMPLETE <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb7/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip.html>
Not related to this change.
John.
Quoted 771 lines
*
New tests
New tests have been introduced between
CI_DRM_11110_fullandPatchwork_22027_full:New IGT tests (1)
* igt@i915_query@hwconfig_table:
o Statuses : 7 skip(s)
o Exec time: [0.0] sKnown issues
Here are the changes found in
Patchwork_22027_fullthat come from known issues:CI changes
Issues hit
* boot:
o shard-glk: (PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk7/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk7/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk7/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk6/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk6/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk6/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk4/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk4/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk1/boot.html>) -> (PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk7/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk2/boot.html>, FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk4/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk4/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk4/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/boot.html>) ([i915#4392]) IGT changes Issues hit*
igt@gem_ctx_persistence@process: o shard-snb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-snb6/igt@[email protected]> ([fdo#109271] / [i915#1099]) +2 similar issues*
igt@gem_eio@in-flight-contexts-10ms: o shard-tglb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-tglb6/igt@[email protected]> -> TIMEOUT <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb8/igt@[email protected]> ([i915#3063])*
igt@gem_eio@unwedge-stress: o shard-iclb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-iclb1/igt@[email protected]> -> TIMEOUT <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb5/igt@[email protected]> ([i915#2481] / [i915#3070])*
igt@gem_exec_balancer@parallel-out-fence: o shard-iclb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-iclb4/igt@[email protected]> -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb6/igt@[email protected]> ([i915#4525]) +1 similar issue*
igt@gem_exec_fair@basic-none-share@rcs0: o shard-iclb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-iclb8/igt@gem_exec_fair@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb4/igt@gem_exec_fair@[email protected]> ([i915#2842])*
igt@gem_exec_fair@basic-none@vcs1: o shard-iclb: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb1/igt@gem_exec_fair@[email protected]> ([i915#2842])*
igt@gem_exec_fair@basic-pace-share@rcs0: o shard-tglb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-tglb5/igt@gem_exec_fair@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb7/igt@gem_exec_fair@[email protected]> ([i915#2842])*
igt@gem_exec_fair@basic-pace-solo@rcs0: o shard-apl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl4/igt@gem_exec_fair@[email protected]> ([i915#2842])*
igt@gem_exec_fair@basic-throttle@rcs0: o shard-glk: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk5/igt@gem_exec_fair@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/igt@gem_exec_fair@[email protected]> ([i915#2842])*
igt@gem_exec_params@secure-non-root: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb6/igt@[email protected]> ([fdo#112283])*
igt@gem_exec_whisper@basic-contexts-forked-all: o shard-glk: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk3/igt@[email protected]> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk4/igt@[email protected]> ([i915#118])*
igt@gem_huc_copy@huc-copy: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl4/igt@[email protected]> ([fdo#109271] / [i915#2190])*
igt@gem_lmem_swapping@heavy-random: o shard-kbl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl7/igt@[email protected]> ([fdo#109271] / [i915#4613]) +1 similar issue*
igt@gem_lmem_swapping@parallel-random: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl2/igt@[email protected]> ([fdo#109271] / [i915#4613])*
igt@gem_pxp@reject-modify-context-protection-off-3: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb2/igt@[email protected]> ([i915#4270]) o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb2/igt@[email protected]> ([i915#4270])*
igt@gem_render_copy@y-tiled-ccs-to-y-tiled-mc-ccs: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb4/igt@[email protected]> ([i915#768])*
igt@gem_softpin@allocator-evict-all-engines: o shard-glk: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk7/igt@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk2/igt@[email protected]> ([i915#4171])*
igt@gem_userptr_blits@dmabuf-sync: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl8/igt@[email protected]> ([fdo#109271] / [i915#3323])*
igt@gem_workarounds@suspend-resume-context: o shard-kbl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-kbl3/igt@[email protected]> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl7/igt@[email protected]> ([i915#180])*
igt@gen9_exec_parse@secure-batches: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb3/igt@[email protected]> ([i915#2856]) o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb2/igt@[email protected]> ([i915#2527] / [i915#2856]) +1 similar issue*
igt@i915_pm_dc@dc6-dpms: o shard-skl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl3/igt@[email protected]> ([i915#454])*
igt@i915_pm_dc@dc6-psr: o shard-iclb: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb4/igt@[email protected]> ([i915#454]) o shard-tglb: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb6/igt@[email protected]> ([i915#454])*
igt@i915_query@query-topology-unsupported: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb1/igt@[email protected]> ([fdo#109302]) o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@[email protected]> ([fdo#109302])*
igt@kms_big_fb@linear-8bpp-rotate-90: o shard-glk: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk7/igt@[email protected]> ([fdo#109271]) +36 similar issues o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@[email protected]> ([fdo#111614]) +1 similar issue*
igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-async-flip: o shard-skl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl10/igt@[email protected]> ([i915#3743]) +1 similar issue*
igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip: o shard-apl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl4/igt@[email protected]> ([fdo#109271] / [i915#3777])*
igt@kms_big_fb@y-tiled-64bpp-rotate-90: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb8/igt@[email protected]> ([fdo#110725] / [fdo#111614]) +1 similar issue*
igt@kms_big_fb@yf-tiled-8bpp-rotate-180: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb8/igt@[email protected]> ([fdo#111615]) +1 similar issue*
igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl10/igt@[email protected]> ([fdo#109271] / [i915#3777]) +2 similar issues*
igt@kms_busy@extended-modeset-hang-newfb: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl2/igt@[email protected]> ([fdo#109271]) +173 similar issues*
igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs: o shard-apl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl6/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html> ([fdo#109271] / [i915#3886]) +5 similar issues o shard-glk: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html> ([fdo#109271] / [i915#3886]) +1 similar issue*
igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_mc_ccs: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb3/igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_mc_ccs.html> ([fdo#109278] / [i915#3886]) +3 similar issues*
igt@kms_ccs@pipe-b-crc-primary-basic-yf_tiled_ccs: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb2/igt@kms_ccs@pipe-b-crc-primary-basic-yf_tiled_ccs.html> ([fdo#111615] / [i915#3689]) +2 similar issues*
igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs: o shard-kbl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl7/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html> ([fdo#109271] / [i915#3886]) +6 similar issues*
igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_rc_ccs_cc: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl4/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_rc_ccs_cc.html> ([fdo#109271] / [i915#3886]) +8 similar issues*
igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_ccs: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb3/igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_ccs.html> ([i915#3689])*
igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html> ([i915#3689] / [i915#3886]) +4 similar issues*
igt@kms_color@pipe-b-ctm-negative: o shard-skl: NOTRUN -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl4/igt@[email protected]> ([i915#1982])*
igt@kms_color@pipe-d-ctm-blue-to-red: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb2/igt@[email protected]> ([fdo#109278] / [i915#1149])*
igt@kms_color_chamelium@pipe-a-ctm-0-25: o shard-snb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-snb5/igt@[email protected]> ([fdo#109271] / [fdo#111827]) +3 similar issues*
igt@kms_color_chamelium@pipe-a-ctm-blue-to-red: o shard-kbl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl1/igt@[email protected]> ([fdo#109271] / [fdo#111827]) +10 similar issues*
igt@kms_color_chamelium@pipe-c-ctm-0-25: o shard-apl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl1/igt@[email protected]> ([fdo#109271] / [fdo#111827]) +5 similar issues*
igt@kms_color_chamelium@pipe-c-ctm-max: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb2/igt@[email protected]> ([fdo#109284] / [fdo#111827]) +2 similar issues*
igt@kms_color_chamelium@pipe-d-degamma: o shard-glk: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk6/igt@[email protected]> ([fdo#109271] / [fdo#111827]) +3 similar issues o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl3/igt@[email protected]> ([fdo#109271] / [fdo#111827]) +16 similar issues o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@[email protected]> ([fdo#109284] / [fdo#111827]) +6 similar issues o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb1/igt@[email protected]> ([fdo#109278] / [fdo#109284] / [fdo#111827])*
igt@kms_content_protection@atomic: o shard-kbl: NOTRUN -> TIMEOUT <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl7/igt@[email protected]> ([i915#1319])*
igt@kms_content_protection@uevent: o shard-kbl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl1/igt@[email protected]> ([i915#2105]) o shard-apl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl4/igt@[email protected]> ([i915#2105])*
igt@kms_cursor_crc@pipe-a-cursor-512x512-random: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb1/igt@[email protected]> ([fdo#109278] / [fdo#109279])*
igt@kms_cursor_crc@pipe-c-cursor-max-size-offscreen: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@[email protected]> ([i915#3359]) +1 similar issue*
igt@kms_cursor_crc@pipe-c-cursor-suspend: o shard-skl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-skl6/igt@[email protected]> -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl2/igt@[email protected]> ([fdo#109271]) +15 similar issues*
igt@kms_cursor_crc@pipe-d-cursor-512x512-onscreen: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb2/igt@[email protected]> ([fdo#109279] / [i915#3359]) +1 similar issue*
igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge: o shard-snb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-snb6/igt@[email protected]> ([fdo#109271]) +81 similar issues*
igt@kms_cursor_legacy@cursorb-vs-flipa-atomic: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb3/igt@[email protected]> ([fdo#109274] / [fdo#109278])*
igt@kms_cursor_legacy@cursorb-vs-flipb-atomic: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb1/igt@[email protected]> ([fdo#109274] / [fdo#111825]) +2 similar issues*
igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
o shard-iclb: NOTRUN -> FAIL
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html>
([i915#2346])
*igt@kms_cursor_legacy@pipe-d-single-move: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb3/igt@[email protected]> ([fdo#109278]) +11 similar issues*
igt@kms_fbcon_fbt@fbc-suspend: o shard-kbl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-kbl3/igt@[email protected]> -> INCOMPLETE <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl4/igt@[email protected]> ([i915#180] / [i915#636])*
igt@kms_flip@2x-plain-flip-fb-recreate: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb1/igt@[email protected]> ([fdo#109274])*
igt@kms_flip@flip-vs-expired-vblank@b-edp1: o shard-skl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-skl8/igt@kms_flip@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl1/igt@kms_flip@[email protected]> ([i915#79])*
igt@kms_flip@flip-vs-suspend@c-dp1: o shard-kbl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-kbl1/igt@kms_flip@[email protected]> -> INCOMPLETE <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl3/igt@kms_flip@[email protected]> ([i915#636])*
igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb6/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling.html> ([i915#2587])*
igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-indfb-draw-mmap-cpu: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-iclb6/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-indfb-draw-mmap-cpu.html> ([fdo#109280]) +9 similar issues*
igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-render: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-tglb6/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-render.html> ([fdo#109280] / [fdo#111825]) +12 similar issues*
igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc: o shard-kbl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl6/igt@[email protected]> ([fdo#109271]) +146 similar issues*
igt@kms_hdr@bpc-switch-suspend: o shard-skl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-skl8/igt@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl10/igt@[email protected]> ([i915#1188])*
igt@kms_pipe_crc_basic@nonblocking-crc-pipe-d-frame-sequence: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl6/igt@[email protected]> ([fdo#109271] / [i915#533])*
igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes: o shard-apl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-apl7/igt@kms_plane@[email protected]> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl3/igt@kms_plane@[email protected]> ([i915#180]) +4 similar issues*
igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes: o shard-kbl: NOTRUN -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl6/igt@kms_plane@[email protected]> ([i915#180]) +1 similar issue*
igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb: o shard-skl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl1/igt@[email protected]> ([i915#265])*
igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb: o shard-apl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-apl6/igt@[email protected]> ([i915#265])*
igt@kms_plane_alpha_blend@pipe-c-alpha-7efc: o shard-kbl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl6/igt@[email protected]> ([fdo#108145] / [i915#265])*
igt@kms_plane_alpha_blend@pipe-c-alpha-basic: o shard-skl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl10/igt@[email protected]> ([fdo#108145] / [i915#265]) +2 similar issues*
igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb: o shard-kbl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-kbl6/igt@[email protected]> ([i915#265])*
igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min: o shard-skl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-skl8/igt@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-skl7/igt@[email protected]> ([fdo#108145] / [i915#265]) +1 similar issue*
igt@kms_plane_lowres@pipe-a-tiling-y: o shard-glk: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11110/shard-glk8/igt@[email protected]> -> DMESG-FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22027/shard-glk3> ([i915#118] / [i915#1888])
++
-----Original Message-----
From: Harrison, John C <[email protected]>
Sent: Wednesday, January 19, 2022 9:36 PM
To: [email protected]
Cc: [email protected]; Harrison, John C <[email protected]>; Cencelewska, Katarzyna <[email protected]>; Ye, Tony <[email protected]>; Jason Ekstrand <[email protected]>; Brost, Matthew <[email protected]>
Subject: [PATCH v3 0/2] Add support for querying hw info that UMDs need
From: John Harrison <[email protected]>
Various UMDs require hardware configuration information about the current platform. A bunch of static information is available in a fixed table that can be retrieved from the GuC.
v2: Rebased to newer baseline and added a kerneldoc comment.
v3: Rebased to newer baseline and newer GuC interface.
Test-with: [email protected]
UMD: https://github.com/intel/compute-runtime/pull/432/files
UMD: https://github.com/intel/media-driver/pull/1239/files
John Harrison (1):
drm/i915/guc: Add fetch of hwconfig table
Rodrigo Vivi (1):
drm/i915/uapi: Add query for hwconfig table
drivers/gpu/drm/i915/Makefile | 1 + .../gpu/drm/i915/gt/uc/abi/guc_actions_abi.h | 1 + .../gpu/drm/i915/gt/uc/abi/guc_errors_abi.h | 4 + drivers/gpu/drm/i915/gt/uc/intel_guc.h | 3 + .../gpu/drm/i915/gt/uc/intel_guc_hwconfig.c | 151 ++++++++++++++++++ .../gpu/drm/i915/gt/uc/intel_guc_hwconfig.h | 19 +++ drivers/gpu/drm/i915/gt/uc/intel_uc.c | 6 + drivers/gpu/drm/i915/i915_query.c | 23 +++ include/uapi/drm/i915_drm.h | 1 + 9 files changed, 209 insertions(+) create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.h
--
2.25.1
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.
Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.