Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"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>,
	"Wajdeczko, Michal" <Michal.Wajdeczko@intel.com>,
	"Mrozek, Michal" <michal.mrozek@intel.com>
Subject: Re: [PATCH v12 5/5] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl
Date: Wed, 26 Mar 2025 01:45:26 +0200	[thread overview]
Message-ID: <Z-NAFqRhGK4Vjfv5@black.fi.intel.com> (raw)
In-Reply-To: <CH0PR11MB5444B65CB663C9123B41F7CFE5A72@CH0PR11MB5444.namprd11.prod.outlook.com>

On Tue, Mar 25, 2025 at 08:15:59PM +0530, Cavitt, Jonathan wrote:
> From: Jadav, Raag <raag.jadav@intel.com> 
> > On Mon, Mar 24, 2025 at 11:09:28PM +0000, Jonathan Cavitt wrote:
> > > Add support for userspace to request a list of observed faults
> > > from a specified VM.
> > 
> > ...
> > 
> > > v10:
> > > - Remove unnecessary switch case logic (Raag)
> > 
> > This is usually "changes present in version" and not "comments received
> > in version" but I guess this must be one of those drm things.
> 
> I'm fairly certain change logs are supposed to be written in the future tense.
> Or at the very least, I think I picked up the habit in college.  Is this not correct?

I meant it belongs to v11.

> > > +static int xe_vm_get_property_helper(struct xe_vm *vm,
> > > +				     struct drm_xe_vm_get_property *args)
> > > +{
> > > +	int size;
> > > +
> > > +	switch (args->property) {
> > > +	case DRM_XE_VM_GET_PROPERTY_FAULTS:
> > > +		spin_lock(&vm->faults.lock);
> > > +		size = size_mul(sizeof(struct xe_vm_fault), vm->faults.len);
> > > +		spin_unlock(&vm->faults.lock);
> > > +
> > > +		if (args->size)
> > > +			/*
> > > +			 * Number of faults may increase between calls to
> > > +			 * xe_vm_get_property_ioctl, so just report the
> > > +			 * number of faults the user requests if it's less
> > > +			 * than or equal to the number of faults in the VM
> > > +			 * fault array.
> > > +			 */
> > > +			return args->size <= size ? fill_faults(vm, args) : -EINVAL;
> > 
> > You're comparing an int with u32 and I'm not sure how this plays out.
> > The usual practice is to use size_t (even in the struct) 
> 
> Size is a u32 in struct drm_xe_device_query.

And what about the local one?

Raag

  reply	other threads:[~2025-03-25 23:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24 23:09 [PATCH v12 0/5] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl Jonathan Cavitt
2025-03-24 23:09 ` [PATCH v12 1/5] drm/xe/xe_gt_pagefault: Disallow writes to read-only VMAs Jonathan Cavitt
2025-03-24 23:09 ` [PATCH v12 2/5] drm/xe/xe_gt_pagefault: Move pagefault struct to header Jonathan Cavitt
2025-03-24 23:09 ` [PATCH v12 3/5] drm/xe/uapi: Define drm_xe_vm_get_property Jonathan Cavitt
2025-03-24 23:09 ` [PATCH v12 4/5] drm/xe/xe_vm: Add per VM fault info Jonathan Cavitt
2025-03-24 23:09 ` [PATCH v12 5/5] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl Jonathan Cavitt
2025-03-25  7:39   ` Raag Jadav
2025-03-25 14:45     ` Cavitt, Jonathan
2025-03-25 23:45       ` Raag Jadav [this message]
2025-03-26 14:21         ` Cavitt, Jonathan
2025-03-26 15:30           ` Raag Jadav
2025-03-25 18:09   ` Jianxun Zhang
2025-03-24 23:41 ` ✓ CI.Patch_applied: success for drm/xe/xe_vm: Implement xe_vm_get_property_ioctl (rev13) Patchwork
2025-03-24 23:41 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-24 23:43 ` ✓ CI.KUnit: success " Patchwork
2025-03-24 23:59 ` ✓ CI.Build: " Patchwork
2025-03-25  0:01 ` ✗ CI.Hooks: failure " Patchwork
2025-03-25  0:03 ` ✓ CI.checksparse: success " Patchwork
2025-03-25  0:24 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-25  5:11 ` ✗ Xe.CI.Full: failure " 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=Z-NAFqRhGK4Vjfv5@black.fi.intel.com \
    --to=raag.jadav@intel.com \
    --cc=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=michal.mrozek@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