From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Trim gen11_gt_irq_handler
Date: Fri, 9 Mar 2018 10:06:48 +0000 [thread overview]
Message-ID: <25b5ad32-1cc4-1988-eed3-e0f115302eb2@linux.intel.com> (raw)
In-Reply-To: <152055949153.10591.5224058937124611565@mail.alporthouse.com>
On 09/03/2018 01:38, Chris Wilson wrote:
> Quoting Chris Wilson (2018-03-09 01:33:08)
>> gen11_gt_engine_intr(struct drm_i915_private * const i915,
>> const unsigned int bank, const unsigned int bit)
>> @@ -2836,10 +2798,23 @@ static void
>> gen11_gt_irq_handler(struct drm_i915_private * const i915,
>> const u32 master_ctl)
>> {
>> + static const u8 bank0_map[] = {
>> + [GEN11_RCS0] = RCS,
>> + [GEN11_BCS] = BCS,
> Is there a reason why its RCS0 but BCS? And the multi-instance classes
> actually use VCS(x)?
I am pretty sure that naming came from the spec.
Side note - one thing I dislike a bit about the current code and this
patch is that all engines have to be enumerated explicitly in the
interrupt handler. I kind of thought it was handy to handle the
multi-class engines from a loop, and so have one place less to remember
to update after adding a new engine instance.
And in general I think too many bike-sheds on this area of code before
we are even running it on real hw. :(
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-09 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 1:27 [PATCH 1/2] drm/i915: Push irq_shift from gen8_cs_irq_handler() to caller Chris Wilson
2018-03-09 1:27 ` [PATCH 2/2] drm/i915: Trim gen11_gt_irq_handler Chris Wilson
2018-03-09 1:33 ` [PATCH v2] " Chris Wilson
2018-03-09 1:38 ` Chris Wilson
2018-03-09 10:06 ` Tvrtko Ursulin [this message]
2018-03-09 10:17 ` Chris Wilson
2018-03-09 19:14 ` Daniele Ceraolo Spurio
2018-03-09 2:21 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Push irq_shift from gen8_cs_irq_handler() to caller (rev2) Patchwork
2018-03-09 7:05 ` ✗ Fi.CI.IGT: warning " 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=25b5ad32-1cc4-1988-eed3-e0f115302eb2@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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 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.