From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [RFC v2 1/6] drm/xe/xe2: Support flat ccs.
Date: Fri, 24 Nov 2023 12:02:26 +0100 [thread overview]
Message-ID: <0a468d2ac94069233f474bf6c965d8deeacc70e5.camel@linux.intel.com> (raw)
In-Reply-To: <20231121100906.3587649-2-himal.prasad.ghimiray@intel.com>
Hi,
On Tue, 2023-11-21 at 15:39 +0530, Himal Prasad Ghimiray wrote:
> Enable flat ccs for XE2_GFX_FEATURES.
>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Himal Prasad Ghimiray
> <himal.prasad.ghimiray@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Typically you add the implementation first and then enable it, so this
patch should go last. (Rule is the driver should not misbehave if
bisecting lands in the middle of a patch series).
/Thomas
>
> diff --git a/drivers/gpu/drm/xe/xe_pci.c
> b/drivers/gpu/drm/xe/xe_pci.c
> index 682ba188e456..d9754f3d45f7 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
> @@ -157,7 +157,7 @@ static const struct xe_graphics_desc
> graphics_xelpg = {
> #define XE2_GFX_FEATURES \
> .dma_mask_size = 46, \
> .has_asid = 1, \
> - .has_flat_ccs = 0 /* FIXME: implementation missing */, \
> + .has_flat_ccs = 1, \
> .has_range_tlb_invalidation = 1, \
> .supports_usm = 0 /* FIXME: implementation missing */, \
> .va_bits = 48, \
next prev parent reply other threads:[~2023-11-24 11:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 10:09 [Intel-xe] [RFC v2 0/6] Enable compression handling on LNL Himal Prasad Ghimiray
2023-11-21 10:09 ` [Intel-xe] [RFC v2 1/6] drm/xe/xe2: Support flat ccs Himal Prasad Ghimiray
2023-11-23 16:28 ` Matthew Auld
2023-11-27 3:04 ` Ghimiray, Himal Prasad
2023-11-24 11:02 ` Thomas Hellström [this message]
2023-11-27 3:05 ` Ghimiray, Himal Prasad
2023-11-21 10:09 ` [Intel-xe] [RFC v2 2/6] drm/xe/xe2: Determine bios enablement for flat ccs on igfx Himal Prasad Ghimiray
2023-11-23 16:37 ` Matthew Auld
2023-11-23 17:01 ` Matthew Auld
2023-11-27 3:11 ` Ghimiray, Himal Prasad
2023-11-24 11:05 ` Thomas Hellström
2023-11-27 3:12 ` Ghimiray, Himal Prasad
2023-11-21 10:09 ` [Intel-xe] [RFC v2 3/6] drm/xe/xe2: Allocate extra pages for ccs during bo create Himal Prasad Ghimiray
2023-11-24 11:09 ` Thomas Hellström
2023-11-27 3:19 ` Ghimiray, Himal Prasad
2023-11-27 9:41 ` Thomas Hellström
2023-11-29 4:53 ` Ghimiray, Himal Prasad
2023-11-21 10:09 ` [Intel-xe] [RFC v2 4/6] drm/xe/xe2: Updates on XY_CTRL_SURF_COPY_BLT Himal Prasad Ghimiray
2023-11-24 11:11 ` Thomas Hellström
2023-11-27 3:21 ` Ghimiray, Himal Prasad
2023-11-21 10:09 ` [Intel-xe] [RFC v2 5/6] drm/xe/xe_migrate.c: Use NULL 1G PTE mapped at 255GiB VA for ccs clear Himal Prasad Ghimiray
2023-11-24 11:19 ` Thomas Hellström
2023-11-27 3:23 ` Ghimiray, Himal Prasad
2023-11-21 10:09 ` [Intel-xe] [RFC v2 6/6] drm/xe/xe2: Handle flat ccs move for igfx Himal Prasad Ghimiray
2023-11-24 15:48 ` Thomas Hellström
2023-11-27 3:25 ` Ghimiray, Himal Prasad
2023-11-28 13:36 ` [Intel-xe] [RFC v2 0/6] Enable compression handling on LNL Thomas Hellström
2023-11-29 4:49 ` Ghimiray, Himal Prasad
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=0a468d2ac94069233f474bf6c965d8deeacc70e5.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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