From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>,
Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>,
"Garg, Nemesa" <nemesa.garg@intel.com>,
"Roper, Matthew D" <matthew.d.roper@intel.com>
Subject: Re: [PATCH] lib: sync i915_pciids.h with kernel
Date: Fri, 05 Jan 2024 15:26:23 +0200 [thread overview]
Message-ID: <87plyfykqo.fsf@intel.com> (raw)
In-Reply-To: <7297abc4-309a-4ca8-a606-498b3abd0c2a@intel.com>
On Fri, 22 Dec 2023, Lionel Landwerlin <lionel.g.landwerlin@intel.com> wrote:
> The reason we need to differentiate GT2/GT3 skus is that they require a
> different programming to get performance metrics.
Please explain why this isn't abstracted in the kernel, and why this
needs PCI ID level identification in userspace.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-01-05 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 9:08 [PATCH] lib: sync i915_pciids.h with kernel Chaitanya Kumar Borah
2023-12-12 10:24 ` ✗ CI.xeBAT: failure for lib: sync i915_pciids.h with kernel (rev14) Patchwork
2023-12-13 13:17 ` [PATCH] lib: sync i915_pciids.h with kernel Juha-Pekka Heikkila
2023-12-14 4:48 ` Borah, Chaitanya Kumar
2023-12-14 14:36 ` Kamil Konieczny
2023-12-18 10:14 ` Borah, Chaitanya Kumar
2023-12-18 16:19 ` Kamil Konieczny
2023-12-19 5:43 ` Borah, Chaitanya Kumar
2023-12-19 7:00 ` Kamil Konieczny
2023-12-22 12:18 ` Lionel Landwerlin
2024-01-05 13:26 ` Jani Nikula [this message]
2024-01-05 13:35 ` Lionel Landwerlin
2024-01-05 13:47 ` Jani Nikula
2023-12-14 5:03 ` ✗ Fi.CI.BUILD: failure for lib: sync i915_pciids.h with kernel (rev15) Patchwork
2024-03-27 20:12 [PATCH] lib: sync i915_pciids.h with kernel Ravi Kumar Vodapalli
2024-03-28 19:32 ` Matt Roper
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=87plyfykqo.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=lionel.g.landwerlin@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=nemesa.garg@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.