From: "Tauro, Riana" <riana.tauro@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
<rodrigo.vivi@intel.com>, <aravind.iddamsetty@linux.intel.com>,
<badal.nilawar@intel.com>, <ravi.kishore.koppuravuri@intel.com>,
<mallesh.koujalagi@intel.com>
Subject: Re: [PATCH 4/5] drm/xe/xe_ras: Add structures and commands for get counter
Date: Tue, 7 Apr 2026 13:28:19 +0530 [thread overview]
Message-ID: <4e78f363-7577-49ba-9652-68cb81a5fd4f@intel.com> (raw)
In-Reply-To: <adS2D9Ea2DQZ-YdG@black.igk.intel.com>
On 4/7/2026 1:15 PM, Raag Jadav wrote:
> On Mon, Apr 06, 2026 at 10:53:13AM +0530, Tauro, Riana wrote:
>> On 4/1/2026 1:28 PM, Raag Jadav wrote:
>>> On Fri, Mar 20, 2026 at 03:55:59PM +0530, Riana Tauro wrote:
> ...
>
>>>> + /** @flags: Info queue control flags */
>>>> + u32 flags:8;
>>> Why not u8?
>> flags, compression type and reserved are part of u32.
>>
>> It's in-line with the firmware definition.
>>
>> Also it is not recommended to mix the types if the bit fields belong to the
>> same type.
> By who? I thought it was just matter of readability since we already have
> __packed in place? Anyway, I'll leave it upto you.
C specification
"An implementation may allocate any addressable storage unit large
enough to hold a bit-field. If enough space remains, a bit-field that
immediately follows another bit-field in a structure shall be packed
into adjacent bits of the same unit.
If insufficient space remains, whether a bit-field that does not fit is
put into the next unit or overlaps adjacent units is implementation-defined"
It says it is upto the compiler and is implementation defined.
Retaining this unless there is an issue.
Thanks
Riana
>
> Raag
>
>>>> + /** @compression_type: Compression type used for this chunk */
>>>> + u32 compression_type:4;
>>> Ditto.
>>>
>>>> + /** @reserved: Reserved for future use */
>>>> + u32 reserved:20;
>>>> + /** @checksum: Checksum of the chunk data */
>>>> + u32 checksum;
>>>> +} __packed;
next prev parent reply other threads:[~2026-04-07 7:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 10:25 [PATCH 0/5] Add get-error-counter support for CRI Riana Tauro
2026-03-20 10:25 ` [PATCH 1/5] drm/xe/xe_sysctrl: Add System controller patch Riana Tauro
2026-03-20 10:25 ` [PATCH 2/5] drm/xe/uapi: Add additional error components to XE DRM RAS Riana Tauro
2026-03-25 9:24 ` Aravind Iddamsetty
2026-03-20 10:25 ` [PATCH 3/5] drm/xe/ras: Add flag for Xe RAS Riana Tauro
2026-04-01 7:53 ` Raag Jadav
2026-04-06 5:25 ` Tauro, Riana
2026-03-20 10:25 ` [PATCH 4/5] drm/xe/xe_ras: Add structures and commands for get counter Riana Tauro
2026-04-01 7:58 ` Raag Jadav
2026-04-06 5:23 ` Tauro, Riana
2026-04-07 7:45 ` Raag Jadav
2026-04-07 7:58 ` Tauro, Riana [this message]
2026-03-20 10:26 ` [PATCH 5/5] drm/xe/xe_ras: Add support to query error counter for CRI Riana Tauro
2026-04-01 8:08 ` Raag Jadav
2026-04-06 7:29 ` Tauro, Riana
2026-03-20 10:33 ` ✗ CI.checkpatch: warning for Add get-error-counter support " Patchwork
2026-03-20 10:35 ` ✓ CI.KUnit: success " Patchwork
2026-03-20 11:16 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-21 8:10 ` ✓ Xe.CI.FULL: success " 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=4e78f363-7577-49ba-9652-68cb81a5fd4f@intel.com \
--to=riana.tauro@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=ravi.kishore.koppuravuri@intel.com \
--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