Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 6/6] drm/i915/irq: split ILK display irq handling
Date: Tue, 23 Sep 2025 17:17:28 +0300	[thread overview]
Message-ID: <3efae7d2b0923c802545dd763ae3f2241426d1ad@intel.com> (raw)
In-Reply-To: <aM1LXLkz8j1serrU@intel.com>

On Fri, 19 Sep 2025, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Fri, Sep 19, 2025 at 12:51:49PM +0300, Jani Nikula wrote:
>> +void ilk_display_irq_master_disable(struct intel_display *display, u32 *de_ier, u32 *sde_ier)
>> +{
>> +	/* disable master interrupt before clearing iir  */
>> +	*de_ier = intel_de_read(display, DEIER);
>> +	intel_de_write(display, DEIER, *de_ier & ~DE_MASTER_IRQ_CONTROL);
>
> The original used completely unlocked register accessors. Assuming that
> has been working all along without hangs I don't really want to
> re-introduce the lock again. I recently looked at some profiles and
> the irq handlers showed up fairly prominently so making these a lot
> more expensive isn't really desirable. So I'd go with the _fw() variant
> for this stuff.
>
> I've already written a patch that I was planning to send at some point
> that switches all the bdw+ display irq handlers to _fw() to reduce the
> overhead a bit. Would be nice if we could do the same for all the
> earlier platforms too, or at least not make it much more expensive
> than it already is.

Ack. I was actually going to use _fw, but I don't know what happened
between brain and keyboard. :/

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-09-23 14:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19  9:51 [PATCH 0/6] drm/i915/irq: display irq refactoring Jani Nikula
2025-09-19  9:51 ` [PATCH 1/6] drm/i915/irq: drop intel_psr_regs.h include Jani Nikula
2025-09-19  9:51 ` [PATCH 2/6] drm/i915/irq: initialize gen2_imr_mask in terms of enable_mask Jani Nikula
2025-09-19  9:51 ` [PATCH 3/6] drm/i915/irq: abstract i9xx_display_irq_enable_mask() Jani Nikula
2025-09-19  9:51 ` [PATCH 4/6] drm/i915/irq: move check for HAS_HOTPLUG() inside i9xx_hpd_irq_ack() Jani Nikula
2025-09-19  9:51 ` [PATCH 5/6] drm/i915/irq: change ILK irq handling order Jani Nikula
2025-09-19  9:51 ` [PATCH 6/6] drm/i915/irq: split ILK display irq handling Jani Nikula
2025-09-19 12:10   ` Ville Syrjälä
2025-09-23 14:15     ` Jani Nikula
2025-09-19 12:23   ` Ville Syrjälä
2025-09-23 14:17     ` Jani Nikula [this message]
2025-09-19  9:58 ` ✗ CI.checkpatch: warning for drm/i915/irq: display irq refactoring Patchwork
2025-09-19  9:59 ` ✓ CI.KUnit: success " Patchwork
2025-09-19 18:42 ` ✗ Xe.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=3efae7d2b0923c802545dd763ae3f2241426d1ad@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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