From: Matthew Auld <matthew.auld@intel.com>
To: Ramalingam C <ramalingam.c@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/perf: Skip the i915_perf_init for dg2
Date: Tue, 15 Feb 2022 13:03:22 +0000 [thread overview]
Message-ID: <94582ad9-5ebc-73b2-6521-3563cd067d3a@intel.com> (raw)
In-Reply-To: <20220215053115.6023-1-ramalingam.c@intel.com>
On 15/02/2022 05:31, Ramalingam C wrote:
> i915_perf is not enabled for dg2 yet, hence skip the feature
> initialization.
>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> ---
> drivers/gpu/drm/i915/i915_perf.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
> index 36f1325baa7d..5ac9604d07b3 100644
> --- a/drivers/gpu/drm/i915/i915_perf.c
> +++ b/drivers/gpu/drm/i915/i915_perf.c
> @@ -4373,6 +4373,10 @@ void i915_perf_init(struct drm_i915_private *i915)
>
> /* XXX const struct i915_perf_ops! */
>
> + /* i915_perf is not enabled for DG2 yet */
> + if (IS_DG2(i915))
> + return;
> +
> perf->oa_formats = oa_formats;
> if (IS_HASWELL(i915)) {
> perf->ops.is_valid_b_counter_reg = gen7_is_valid_b_counter_addr;
next prev parent reply other threads:[~2022-02-15 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 5:31 [Intel-gfx] [PATCH] drm/i915/perf: Skip the i915_perf_init for dg2 Ramalingam C
2022-02-15 13:03 ` Matthew Auld [this message]
2022-02-16 4:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-02-16 10:22 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-17 8:08 ` Ramalingam C
2022-02-17 19:13 ` [Intel-gfx] [PATCH] " Umesh Nerlige Ramappa
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=94582ad9-5ebc-73b2-6521-3563cd067d3a@intel.com \
--to=matthew.auld@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ramalingam.c@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