From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>,
Animesh Manna <animesh.manna@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: Revert "drm/i915: Disable DSB in Xe KMD"
Date: Tue, 27 Aug 2024 17:02:47 +0200 [thread overview]
Message-ID: <ca1b62f5-f09a-44ac-8592-a9881c73e164@linux.intel.com> (raw)
In-Reply-To: <7fe8022e-6d86-4cdf-88a3-b19febfb1006@intel.com>
Hey,
Den 2024-07-09 kl. 12:23, skrev Matthew Auld:
> On 09/07/2024 10:33, Maarten Lankhorst wrote:
>> Hello,
>>
>> I've been trying out this patch, but I'm still seeing corruption on my laptop with DSB enabled.
>> I'd recommend not merging until it is fixed. :)
>
> Just wondering, is it correct to use cpu:wb for the dsb buffer? Does the dsb stuff not suffer from "display is not coherent with gpu/cpu caches"? In i915 it looks to be cpu:wc.
My guess is that could be it. Our kernel mappings are cached by default.
Perhaps I'll look at the DPT code too, it could suffer from the same issue.
Will test a bit more tomorrow :)
~Maarten
>> Cheers,
>> ~Maarten
>>
>> Den 2024-07-08 kl. 07:56, skrev Animesh Manna:
>>> This reverts commit c27f010aa1884276ee5dae72034d84987060c769.
>>>
>>> After fix from [1] dsb timeout issue is not reproducible on local testing
>>> with xe driver. Checking CI result to confirm and not for review.
>>>
>>> [1] https://patchwork.freedesktop.org/series/130783/
>>>
>>> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
>>> ---
>>> drivers/gpu/drm/i915/display/intel_dsb.c | 4 ----
>>> 1 file changed, 4 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/display/intel_dsb.c b/drivers/gpu/drm/i915/display/intel_dsb.c
>>> index 2ab3765f6c06..e9c4835a2c30 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_dsb.c
>>> +++ b/drivers/gpu/drm/i915/display/intel_dsb.c
>>> @@ -463,10 +463,6 @@ struct intel_dsb *intel_dsb_prepare(struct intel_atomic_state *state,
>>> if (!i915->display.params.enable_dsb)
>>> return NULL;
>>> - /* TODO: DSB is broken in Xe KMD, so disabling it until fixed */
>>> - if (!IS_ENABLED(I915))
>>> - return NULL;
>>> -
>>> dsb = kzalloc(sizeof(*dsb), GFP_KERNEL);
>>> if (!dsb)
>>> goto out;
next prev parent reply other threads:[~2024-08-27 15:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 5:56 [PATCH] drm/xe: Revert "drm/i915: Disable DSB in Xe KMD" Animesh Manna
2024-07-08 6:18 ` ✓ CI.Patch_applied: success for drm/xe: Revert "drm/i915: Disable DSB in Xe KMD" (rev4) Patchwork
2024-07-08 6:18 ` ✓ CI.checkpatch: " Patchwork
2024-07-08 6:20 ` ✓ CI.KUnit: " Patchwork
2024-07-08 6:31 ` ✓ CI.Build: " Patchwork
2024-07-08 6:34 ` ✓ CI.Hooks: " Patchwork
2024-07-08 6:35 ` ✗ CI.checksparse: warning " Patchwork
2024-07-08 7:00 ` ✓ CI.BAT: success " Patchwork
2024-07-09 9:33 ` [PATCH] drm/xe: Revert "drm/i915: Disable DSB in Xe KMD" Maarten Lankhorst
2024-07-09 9:40 ` Manna, Animesh
2024-07-09 10:23 ` Matthew Auld
2024-08-27 15:02 ` Maarten Lankhorst [this message]
2024-07-19 8:50 ` ✓ CI.Patch_applied: success for drm/xe: Revert "drm/i915: Disable DSB in Xe KMD" (rev5) Patchwork
2024-07-19 8:50 ` ✓ CI.checkpatch: " Patchwork
2024-07-19 8:51 ` ✓ CI.KUnit: " Patchwork
2024-07-19 9:07 ` ✓ CI.Build: " Patchwork
2024-07-19 9:10 ` ✓ CI.Hooks: " Patchwork
2024-07-19 9:12 ` ✗ CI.checksparse: warning " Patchwork
2024-07-19 9:32 ` ✓ CI.BAT: success " Patchwork
2024-07-19 12:46 ` ✗ CI.FULL: failure " Patchwork
2024-08-27 14:30 ` ✓ CI.Patch_applied: success for drm/xe: Revert "drm/i915: Disable DSB in Xe KMD" (rev6) Patchwork
2024-08-27 14:31 ` ✓ CI.checkpatch: " Patchwork
2024-08-27 14:32 ` ✓ CI.KUnit: " Patchwork
2024-08-27 14:44 ` ✓ CI.Build: " Patchwork
2024-08-27 14:46 ` ✓ CI.Hooks: " Patchwork
2024-08-27 14:47 ` ✗ CI.checksparse: warning " Patchwork
2024-08-27 15:06 ` ✓ CI.BAT: success " Patchwork
2024-08-27 22:08 ` ✗ CI.FULL: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-03-22 11:42 [PATCH] drm/xe: Revert "drm/i915: Disable DSB in Xe KMD" Animesh Manna
2024-03-22 14:04 ` Souza, Jose
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=ca1b62f5-f09a-44ac-8592-a9881c73e164@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=animesh.manna@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@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