From: Jakub Kicinski <kuba@kernel.org>
To: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
netdev@vger.kernel.org, amd-gfx@lists.freedesktop.org,
simona.vetter@ffwll.ch, airlied@gmail.com,
tejas.upadhyay@intel.com, himal.prasad.ghimiray@intel.com,
rodrigo.vivi@intel.com, riana.tauro@intel.com,
raag.jadav@intel.com, joshua.santosh.ranjan@intel.com,
ashwin.kumar.kulkarni@intel.com, pratik.bari@intel.com,
Hawking.Zhang@amd.com, tao.zhou1@amd.com, YiPeng.Chai@amd.com,
jinzhou.su@amd.com, cesun102@amd.com, lijo.lazar@amd.com,
alexander.deucher@amd.com, christian.koenig@amd.com
Subject: Re: [PATCH v2 1/2] drm/xe: Expose retired VRAM pages via drm-ras
Date: Fri, 16 Oct 2026 15:49:13 -0700 [thread overview]
Message-ID: <20261016154913.1af64e88@kernel.org> (raw)
In-Reply-To: <20261007080354.3072751-2-aravind.iddamsetty@linux.intel.com>
On Wed, 7 Oct 2026 13:33:53 +0530 Aravind Iddamsetty wrote:
> + -
> + name: retired-resource-attrs
> + attributes:
> + -
> + name: node-id
> + type: u32
> + doc: Node ID targeted by this retired resource operation.
> + -
> + name: vram-page
> + type: nest
> + nested-attributes: vram-page-attrs
why wrap attrs in a nest? Are you planning to add other resource types
(than a page)? It's a common anti-pattern in Netlink to over-wrap stuff.
> + doc: >-
> + Type-specific payload. The resource type is identified by the
> + node (its node-name); each node reports a single resource type.
> + -
> + name: vram-page-attrs
> + attributes:
> + -
> + name: address
> + type: u64
> + doc: Device address of the retired VRAM page (e.g. DPA).
> + -
> + name: size
> + type: u64
prefer uint
> + doc: Size of the retired VRAM page in bytes.
> + -
> + name: max-pages
> + type: u32
> + doc: >-
> + Maximum VRAM pages that can be retired. Present only in the
> + leading summary entry of the dump (no address/size/status).
> + -
> + name: status
> + type: u32
> + doc: Retirement status of the retired VRAM page.
> + enum: retired-resource-status
> + -
> + name: pad
> + type: pad
And then you won't need pad
next prev parent reply other threads:[~2026-10-16 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 8:03 [PATCH v2 0/2] drm/xe: Expose retired VRAM pages via drm-ras Aravind Iddamsetty
2026-10-07 8:03 ` [PATCH v2 1/2] " Aravind Iddamsetty
2026-10-07 9:28 ` Christian König
2026-10-07 13:55 ` Rodrigo Vivi
2026-10-14 21:40 ` Rodrigo Vivi
2026-10-16 22:49 ` Jakub Kicinski [this message]
2026-10-07 8:03 ` [PATCH v2 2/2] drm/xe: Remove bad VRAM pages debugfs interface Aravind Iddamsetty
2026-10-14 21:41 ` Rodrigo Vivi
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=20261016154913.1af64e88@kernel.org \
--to=kuba@kernel.org \
--cc=Hawking.Zhang@amd.com \
--cc=YiPeng.Chai@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=ashwin.kumar.kulkarni@intel.com \
--cc=cesun102@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jinzhou.su@amd.com \
--cc=joshua.santosh.ranjan@intel.com \
--cc=lijo.lazar@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pratik.bari@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=tao.zhou1@amd.com \
--cc=tejas.upadhyay@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