From: "Souza, Jose" <jose.souza@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH 1/3] drm/xe/uapi: Remove XE_QUERY_CONFIG_FLAGS_USE_GUC
Date: Fri, 21 Jul 2023 20:34:57 +0000 [thread overview]
Message-ID: <dca195f660ec08dbcb5a181543d56c03280c3bc6.camel@intel.com> (raw)
In-Reply-To: <20230721202144.269837-2-rodrigo.vivi@intel.com>
On Fri, 2023-07-21 at 16:19 -0400, Rodrigo Vivi wrote:
> This config is the only real one. If execlist remains in the
> code it will forever be experimental and we shouldn't maintain
> an uapi like that for that experimental piece of code that
> should never be used by real users.
Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_query.c | 3 ---
> include/uapi/drm/xe_drm.h | 1 -
> 2 files changed, 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_query.c b/drivers/gpu/drm/xe/xe_query.c
> index f880c9af1651..56440a27ddba 100644
> --- a/drivers/gpu/drm/xe/xe_query.c
> +++ b/drivers/gpu/drm/xe/xe_query.c
> @@ -191,9 +191,6 @@ static int query_config(struct xe_device *xe, struct drm_xe_device_query *query)
> if (xe_device_get_root_tile(xe)->mem.vram.usable_size)
> config->info[XE_QUERY_CONFIG_FLAGS] =
> XE_QUERY_CONFIG_FLAGS_HAS_VRAM;
> - if (xe->info.enable_guc)
> - config->info[XE_QUERY_CONFIG_FLAGS] |=
> - XE_QUERY_CONFIG_FLAGS_USE_GUC;
> config->info[XE_QUERY_CONFIG_MIN_ALIGNEMENT] =
> xe->info.vram_flags & XE_VRAM_FLAGS_NEED64K ? SZ_64K : SZ_4K;
> config->info[XE_QUERY_CONFIG_VA_BITS] = 12 +
> diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
> index 347351a8f618..790bf27407a5 100644
> --- a/include/uapi/drm/xe_drm.h
> +++ b/include/uapi/drm/xe_drm.h
> @@ -217,7 +217,6 @@ struct drm_xe_query_config {
> #define XE_QUERY_CONFIG_REV_AND_DEVICE_ID 0
> #define XE_QUERY_CONFIG_FLAGS 1
> #define XE_QUERY_CONFIG_FLAGS_HAS_VRAM (0x1 << 0)
> - #define XE_QUERY_CONFIG_FLAGS_USE_GUC (0x1 << 1)
> #define XE_QUERY_CONFIG_MIN_ALIGNEMENT 2
> #define XE_QUERY_CONFIG_VA_BITS 3
> #define XE_QUERY_CONFIG_GT_COUNT 4
next prev parent reply other threads:[~2023-07-21 20:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 20:19 [Intel-xe] [PATCH 0/3] GuC vs Execlist Rodrigo Vivi
2023-07-21 20:19 ` [Intel-xe] [PATCH 1/3] drm/xe/uapi: Remove XE_QUERY_CONFIG_FLAGS_USE_GUC Rodrigo Vivi
2023-07-21 20:34 ` Souza, Jose [this message]
2023-07-21 20:19 ` [Intel-xe] [PATCH 2/3] drm/xe: Invert guc vs execlists parameters and info Rodrigo Vivi
2023-07-21 20:35 ` Souza, Jose
2023-07-21 20:19 ` [Intel-xe] [PATCH 3/3] drm/xe: Kill execlist support Rodrigo Vivi
2023-07-21 20:40 ` Souza, Jose
2023-07-24 8:02 ` Francois Dugast
2023-07-24 12:43 ` Lucas De Marchi
2023-07-25 20:42 ` Rodrigo Vivi
2023-07-21 20:44 ` [Intel-xe] ✓ CI.Patch_applied: success for GuC vs Execlist Patchwork
2023-07-21 20:45 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-21 20:46 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-21 20:50 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-21 20:50 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-21 20:51 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-21 21:18 ` [Intel-xe] ○ CI.BAT: info " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dca195f660ec08dbcb5a181543d56c03280c3bc6.camel@intel.com \
--to=jose.souza@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox