All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "Nikula, Jani" <jani.nikula@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/display: move unordered works to new private workqueue
Date: Thu, 19 Jun 2025 11:11:53 +0000	[thread overview]
Message-ID: <4ca345fee3e5ffdf7afbaae03085a293a13b5265.camel@intel.com> (raw)
In-Reply-To: <dec2c8bb55a45840fbff4b7f319b71ded75a5392@intel.com>

On Thu, 2025-06-19 at 13:48 +0300, Jani Nikula wrote:
> On Thu, 19 Jun 2025, Luca Coelho <luciano.coelho@intel.com> wrote:
> > Create a new unordered workqueue to be used by the display code
> > instead of relying on the i915 one.  Then move all the unordered works
> > used in the display code to use this new queue.
> > 
> > Since this is an unordered workqueue, by definition there can't be any
> > order dependency with non-display works, so no extra care is needed
> > in regard to that.
> > 
> > This is part of the effort to isolate the display code from i915.
> 
> Overall looks good, but I think you missed two uses of
> i915->unordered_wq, one in intel_dmc_wl.c and one in intel_encoder.c.

Huh, how did I miss them? I need to hone my grepping capabilities...

V2 coming in a sec!

--
Cheers,
Luca.

  reply	other threads:[~2025-06-19 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 10:36 [PATCH] drm/i915/display: move unordered works to new private workqueue Luca Coelho
2025-06-19 10:48 ` Jani Nikula
2025-06-19 11:11   ` Coelho, Luciano [this message]
2025-06-19 13:13 ` ✗ i915.CI.BAT: failure for " 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=4ca345fee3e5ffdf7afbaae03085a293a13b5265.camel@intel.com \
    --to=luciano.coelho@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.