From: Matthew Auld <matthew.auld@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 2/2] drm/xe: Use 64K pages for scanout buffers for Xe2
Date: Tue, 9 Jul 2024 12:26:15 +0100 [thread overview]
Message-ID: <2a5772c2-8956-4de9-b4b6-e13260209241@intel.com> (raw)
In-Reply-To: <20240709111231.490440-3-zbigniew.kempczynski@intel.com>
On 09/07/2024 12:12, Zbigniew Kempczyński wrote:
> Set Xe2 platforms to use 64K pages for display.
>
> Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pci.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> index 53b67f39c7d5..b629145d23fa 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
> @@ -177,6 +177,7 @@ static const struct xe_graphics_desc graphics_xe2 = {
> .name = "Xe2_LPG / Xe2_HPG",
>
> XE2_GFX_FEATURES,
> + .vram_flags = XE_VRAM_FLAGS_DISPLAY_NEED64K,
This change will also apply to lnl, but I don't think we have a way of
forcefully getting 64K pages for system memory atm. Do we just need this
for bmg or is it really all of xe2?
> };
>
> static const struct xe_media_desc media_xem = {
next prev parent reply other threads:[~2024-07-09 11:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 11:12 [PATCH 0/2] Restrict Xe2 to use 64K pages for scanout buffers Zbigniew Kempczyński
2024-07-09 11:12 ` [PATCH 1/2] drm/xe: Separate 64K physical allocation for display Zbigniew Kempczyński
2024-07-09 11:12 ` [PATCH 2/2] drm/xe: Use 64K pages for scanout buffers for Xe2 Zbigniew Kempczyński
2024-07-09 11:26 ` Matthew Auld [this message]
2024-07-09 11:57 ` Zbigniew Kempczyński
2024-07-09 12:02 ` Matthew Auld
2024-07-09 11:17 ` ✓ CI.Patch_applied: success for Restrict Xe2 to use 64K pages for scanout buffers Patchwork
2024-07-09 11:17 ` ✓ CI.checkpatch: " Patchwork
2024-07-09 11:19 ` ✓ CI.KUnit: " Patchwork
2024-07-09 11:31 ` ✓ CI.Build: " Patchwork
2024-07-09 11:34 ` ✓ CI.Hooks: " Patchwork
2024-07-09 11:36 ` ✓ CI.checksparse: " Patchwork
2024-07-09 11:57 ` ✓ CI.BAT: " Patchwork
2024-07-09 12:54 ` ✗ CI.FULL: failure " 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=2a5772c2-8956-4de9-b4b6-e13260209241@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=zbigniew.kempczynski@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