From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>
Cc: platform-driver-x86@vger.kernel.org,
intel-xe@lists.freedesktop.org,
Hans de Goede <hdegoede@redhat.com>,
lucas.demarchi@intel.com, rodrigo.vivi@intel.com
Subject: Re: [PATCH 01/10] drm/xe: Correct BMG VSEC header sizing
Date: Sat, 31 May 2025 08:17:33 +0300 (EEST) [thread overview]
Message-ID: <72b57d0f-c4e6-3515-bd46-062f159c4456@linux.intel.com> (raw)
In-Reply-To: <20250530203356.190234-1-michael.j.ruhl@intel.com>
On Fri, 30 May 2025, Michael J. Ruhl wrote:
> The intel_vsec_header information for the crashlog feature
> is incorrect.
>
> Update the VSEC header with correct sizing and count.
Does this warrant a Fixes tag?
> Signed-off-by: Michael J. Ruhl <michael.j.ruhl@intel.com>
> ---
> drivers/gpu/drm/xe/xe_vsec.c | 20 +++++---------------
> 1 file changed, 5 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_vsec.c b/drivers/gpu/drm/xe/xe_vsec.c
> index 3e573b0b7ebd..67238fc57a4d 100644
> --- a/drivers/gpu/drm/xe/xe_vsec.c
> +++ b/drivers/gpu/drm/xe/xe_vsec.c
> @@ -32,28 +32,18 @@ static struct intel_vsec_header bmg_telemetry = {
> .offset = BMG_DISCOVERY_OFFSET,
> };
>
> -static struct intel_vsec_header bmg_punit_crashlog = {
> - .length = 0x10,
> +static struct intel_vsec_header bmg_crashlog = {
> + .length = 0x18,
> .id = VSEC_ID_CRASHLOG,
> - .num_entries = 1,
> - .entry_size = 4,
> + .num_entries = 2,
> + .entry_size = 6,
> .tbir = 0,
> .offset = BMG_DISCOVERY_OFFSET + 0x60,
> };
>
> -static struct intel_vsec_header bmg_oobmsm_crashlog = {
> - .length = 0x10,
> - .id = VSEC_ID_CRASHLOG,
> - .num_entries = 1,
> - .entry_size = 4,
> - .tbir = 0,
> - .offset = BMG_DISCOVERY_OFFSET + 0x78,
> -};
> -
> static struct intel_vsec_header *bmg_capabilities[] = {
> &bmg_telemetry,
> - &bmg_punit_crashlog,
> - &bmg_oobmsm_crashlog,
> + &bmg_crashlog,
Eh, this change goes way beyond what you said in the changelog, was that
intentional? If yes, please describe and justify all the changes (and
consider if some of them belong to a separate patch as it sounds like
there are two or more changes mixed up into this patch).
> NULL
> };
>
>
--
i.
next prev parent reply other threads:[~2025-05-31 5:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 20:33 [PATCH 01/10] drm/xe: Correct BMG VSEC header sizing Michael J. Ruhl
2025-05-30 20:33 ` [PATCH 02/10] platform/x86/intel/pmt: white space cleanup Michael J. Ruhl
2025-05-31 5:19 ` Ilpo Järvinen
2025-05-30 20:33 ` [PATCH 03/10] platform/x86/intel/pmt: use guard(mutex) Michael J. Ruhl
2025-05-31 5:23 ` Ilpo Järvinen
2025-06-02 14:59 ` Ruhl, Michael J
2025-06-02 15:37 ` Ilpo Järvinen
2025-05-30 20:33 ` [PATCH 04/10] platform/x86/intel: refactor endpoint usage Michael J. Ruhl
2025-05-31 5:29 ` Ilpo Järvinen
2025-06-02 15:01 ` Ruhl, Michael J
2025-05-30 20:33 ` [PATCH 05/10] platform/x86/intel/pmt: crashlog binary file endpoint Michael J. Ruhl
2025-05-31 5:36 ` Ilpo Järvinen
2025-06-02 15:02 ` Ruhl, Michael J
2025-05-30 20:33 ` [PATCH 06/10] platform/x86/intel/pmt: decouple sysfs and namespace Michael J. Ruhl
2025-05-30 20:33 ` [PATCH 07/10] platform/x86/intel/pmt: use a version struct Michael J. Ruhl
2025-05-31 5:46 ` Ilpo Järvinen
2025-06-02 17:57 ` Ruhl, Michael J
2025-06-03 7:06 ` Ilpo Järvinen
2025-05-30 20:33 ` [PATCH 08/10] platform/x86/intel/pmt: support BMG crashlog Michael J. Ruhl
2025-05-31 5:52 ` Ilpo Järvinen
2025-06-02 18:00 ` Ruhl, Michael J
2025-05-30 20:33 ` [PATCH 09/10] sysfs debug Michael J. Ruhl
2025-05-31 5:53 ` Ilpo Järvinen
2025-06-02 15:07 ` Ruhl, Michael J
2025-05-31 5:17 ` Ilpo Järvinen [this message]
2025-05-31 5:18 ` [PATCH 01/10] drm/xe: Correct BMG VSEC header sizing Ilpo Järvinen
2025-06-02 14:54 ` Ruhl, Michael J
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=72b57d0f-c4e6-3515-bd46-062f159c4456@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=michael.j.ruhl@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rodrigo.vivi@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