From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Gupta, saurabhg" <saurabhg.gupta@intel.com>,
"Zuo, Alex" <alex.zuo@intel.com>,
"joonas.lahtinen@linux.intel.com"
<joonas.lahtinen@linux.intel.com>,
"Brost, Matthew" <matthew.brost@intel.com>,
"Zhang, Jianxun" <jianxun.zhang@intel.com>,
"Lin, Shuicheng" <shuicheng.lin@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v7 2/6] drm/xe/xe_gt_pagefault: Migrate pagefault struct to header
Date: Tue, 11 Mar 2025 09:26:27 +0100 [thread overview]
Message-ID: <a48a7eb7-67a3-4bf1-a2bd-8907ccee4fc4@intel.com> (raw)
In-Reply-To: <CH0PR11MB544460A0C65718325C0B9656E5D62@CH0PR11MB5444.namprd11.prod.outlook.com>
On 10.03.2025 22:30, Cavitt, Jonathan wrote:
> -----Original Message-----
> From: Wajdeczko, Michal <Michal.Wajdeczko@intel.com>
> Sent: Monday, March 10, 2025 11:20 AM
> To: Cavitt, Jonathan <jonathan.cavitt@intel.com>; intel-xe@lists.freedesktop.org
> Cc: Gupta, saurabhg <saurabhg.gupta@intel.com>; Zuo, Alex <alex.zuo@intel.com>; joonas.lahtinen@linux.intel.com; Brost, Matthew <matthew.brost@intel.com>; Zhang, Jianxun <jianxun.zhang@intel.com>; Lin, Shuicheng <shuicheng.lin@intel.com>; dri-devel@lists.freedesktop.org
> Subject: Re: [PATCH v7 2/6] drm/xe/xe_gt_pagefault: Migrate pagefault struct to header
>>>
>>> On 10.03.2025 18:18, Jonathan Cavitt wrote:
>>>> Migrate the pagefault struct from xe_gt_pagefault.c to the
>>>
>>> nit: we use "migrate" verb for different purposes.
>>> maybe here (and in the title) the plain "move" will be better?
>>>
>>>> xe_gt_pagefault.h header file, along with the associated enum values.
>>>
>>> hmm, all other components have foo_types.h header file as place for own
>>> types and use foo.h header only for function declarations.
>>>
>>> why are we doing it differently here?
>
> xe_gt_pagefault_types.h does not exist and would have to be created to satisfy this
> request. It would also basically only contain the below xe_pagefault struct and its
> related enums. Is this amenable?
it's about the idea, it doesn't matter not how many items you will put
there. You can take a look at few other "small" types.h files:
$ ls -S -1 *types.h | tail -5
xe_ring_ops_types.h
xe_huc_types.h
xe_gt_stats_types.h
xe_sa_types.h
xe_bb_types.h
next prev parent reply other threads:[~2025-03-11 8:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 17:18 [PATCH v7 0/6] drm/xe/xe_vm: Implement xe_vm_get_faults_ioctl Jonathan Cavitt
2025-03-10 17:18 ` [PATCH v7 1/6] drm/xe/xe_gt_pagefault: Disallow writes to read-only VMAs Jonathan Cavitt
2025-03-10 17:18 ` [PATCH v7 2/6] drm/xe/xe_gt_pagefault: Migrate pagefault struct to header Jonathan Cavitt
2025-03-10 18:20 ` Michal Wajdeczko
2025-03-10 21:30 ` Cavitt, Jonathan
2025-03-11 8:26 ` Michal Wajdeczko [this message]
2025-03-10 17:18 ` [PATCH v7 3/6] drm/xe/xe_vm: Add per VM pagefault info Jonathan Cavitt
2025-03-10 18:36 ` Michal Wajdeczko
2025-03-10 17:18 ` [PATCH v7 4/6] drm/xe/uapi: Define drm_xe_vm_get_faults Jonathan Cavitt
2025-03-11 3:17 ` Zhang, Jianxun
2025-03-11 4:50 ` Matthew Brost
2025-03-11 14:11 ` Cavitt, Jonathan
2025-03-12 16:28 ` Zhang, Jianxun
2025-03-12 16:46 ` Cavitt, Jonathan
2025-03-12 4:18 ` Zhang, Jianxun
2025-03-10 17:18 ` [PATCH v7 5/6] drm/xe/xe_gt_pagefault: Add address_type field to pagefaults Jonathan Cavitt
2025-03-10 17:18 ` [PATCH v7 6/6] drm/xe/xe_vm: Implement xe_vm_get_faults_ioctl Jonathan Cavitt
2025-03-10 17:45 ` ✓ CI.Patch_applied: success for drm/xe/xe_vm: Implement xe_vm_get_faults_ioctl (rev2) Patchwork
2025-03-10 17:45 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-10 17:46 ` ✓ CI.KUnit: success " Patchwork
2025-03-10 18:03 ` ✓ CI.Build: " Patchwork
2025-03-10 18:05 ` ✓ CI.Hooks: " Patchwork
2025-03-10 18:06 ` ✓ CI.checksparse: " Patchwork
2025-03-10 18:28 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-11 12:39 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-11 13:57 ` 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=a48a7eb7-67a3-4bf1-a2bd-8907ccee4fc4@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=alex.zuo@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jianxun.zhang@intel.com \
--cc=jonathan.cavitt@intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=saurabhg.gupta@intel.com \
--cc=shuicheng.lin@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