Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>
Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
	rodrigo.vivi@intel.com, daniele.ceraolospurio@intel.com,
	riana.tauro@intel.com, mallesh.koujalagi@intel.com,
	aravind.iddamsetty@intel.com, himal.prasad.ghimiray@intel.com,
	arvind.yadav@intel.com, syed.abdul.muqthyar.ahmed@intel.com,
	nitin.r.gote@intel.com, matthew.d.roper@intel.com
Subject: Re: [PATCH v9 3/3] drm/xe/cper: Prepare Intel CPER info records
Date: Sat, 21 Nov 2026 12:32:41 +0100	[thread overview]
Message-ID: <awGBWR8FyhxaxSTd@black.igk.intel.com> (raw)
In-Reply-To: <20261121064545.168470-8-badal.nilawar@intel.com>

On Sat, Nov 21, 2026 at 12:15:49PM +0530, Badal Nilawar wrote:
> The RAS info queue contains error logs for detail counters, or dynamic
> counter headers followed by error logs for aggregate counters.
> 
> Build CPER info records from the queue data, converting each error log
> into an CPER event. For aggregate counters, group logs by their dynamic
> counter header and build one info record per header.
> 
> Emit a CPER record for each generated info record.
> 
> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>

Reviewed-by: Raag Jadav <raag.jadav@intel.com>

  reply	other threads:[~2026-11-21 11:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-21  6:45 [PATCH v9 0/3] Extend CPER records with RAS info queue data Badal Nilawar
2026-11-21  6:45 ` [PATCH v9 1/3] drm/xe/cper: Drop redundant counter argument Badal Nilawar
2026-11-21  6:45 ` [PATCH v9 2/3] drm/xe/xe_ras: Add support to retrieve info queue data Badal Nilawar
2026-11-21 11:55   ` Raag Jadav
2026-11-21  6:45 ` [PATCH v9 3/3] drm/xe/cper: Prepare Intel CPER info records Badal Nilawar
2026-11-21 11:32   ` Raag Jadav [this message]
2026-11-21  6:55 ` ✓ CI.KUnit: success for Extend CPER records with RAS info queue data (rev4) Patchwork
2026-11-21  7:32 ` ✓ Xe.CI.BAT: " 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=awGBWR8FyhxaxSTd@black.igk.intel.com \
    --to=raag.jadav@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=aravind.iddamsetty@intel.com \
    --cc=arvind.yadav@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=mallesh.koujalagi@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=nitin.r.gote@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=syed.abdul.muqthyar.ahmed@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