All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Deepak R Varma <drv@mailo.com>
Cc: Praveen Kumar <kumarpraveen@linux.microsoft.com>,
	intel-gfx@lists.freedesktop.org,
	Saurabh Singh Sengar <ssengar@microsoft.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	intel-gvt-dev@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/gvt: Avoid full proxy f_ops for vgpu_status debug attributes
Date: Wed, 11 Jan 2023 10:24:22 -0500	[thread overview]
Message-ID: <Y77UpjMG9t3SIkMo@intel.com> (raw)
In-Reply-To: <Y77SsDGaZ8+BjXel@ubun2204.myguest.virtualbox.org>

On Wed, Jan 11, 2023 at 08:46:00PM +0530, Deepak R Varma wrote:
> On Wed, Jan 11, 2023 at 10:00:11AM -0500, Rodrigo Vivi wrote:
> > > > Actually, could you please address the checkpatch issues before we can push?
> > > > Sorry about that, but just noticed now when I was going to push the other ones.
> > > 
> > > Hello Rodrigo,
> > > The checkpatch warning is associated with the long "make coccicheck ..." command
> > > in the commit message. It is not part of the code, so is should not be carried
> > > forward into the code base.
> > > If you still want me to correct it, I will need to split it into two lines which
> > > I think still violates the commit description guidelines.
> > 
> > This part I would just ignore or fix myself while merging. But the next one about
> > the parenthesis alignment need to be fixed in the code so we need another version.
> > Since we try to avoid touching the code between CI and merge.
> 
> I am sorry, but I am unable to locate the "second checkpatch complaint" you are
> referring to. I have received only the following from the checkpatch robot:
> 
> == Summary ==
> 
> Error: dim checkpatch failed
> 4c95e9b71212 drm/i915/gvt: Avoid full proxy f_ops for scan_nonprivbb debug attributes
> -:21: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
> #21:
> make coccicheck M=drivers/gpu/drm/i915/ MODE=patch COCCI=./scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci
> 
> total: 0 errors, 1 warnings, 0 checks, 22 lines checked
> 33d68a01cad3 drm/i915/gvt: Avoid full proxy f_ops for vgpu_status debug attributes
> -:21: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
> #21:
> make coccicheck M=drivers/gpu/drm/i915/ MODE=patch COCCI=./scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci
> 
> total: 0 errors, 1 warnings, 0 checks, 18 lines checked
> 

doh, my bad! this gvt patch is indeed right. up to gvt folks to modify this line
when merging or to ignore...

The problem I mentioned was in the other series. Sorry for the noise.

but for the record:

-:47: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#47: FILE: drivers/gpu/drm/i915/display/intel_drrs.c:386:
+	debugfs_create_file_unsafe("i915_drrs_ctl", 0644, crtc->base.debugfs_entry,
+				    crtc, &intel_drrs_debugfs_ctl_fops);


> ===============================
> 
> > 
> > Then, since you need to change that, while changing that, also please break
> > the coccinelle line in the commit msg.
> > 
> > I'd appreciate to have the patch for the pxp as well :)
> 
> Sure. As mentioned in the other thread, I am looking into it and would submit a
> patch accordingly.
> 
> Thank you,
> ./drv
> 
> > 
> > Thanks a lot,
> > Rodrigo.
> > 
> > 
> > > 
> > > Let me know what you think.
> > > 
> > > Thank you,
> > > ./drv
> > > 
> > > > 
> > > > > 
> > > > > > ---
> > > > > >  drivers/gpu/drm/i915/gvt/debugfs.c | 6 +++---
> > > > > >  1 file changed, 3 insertions(+), 3 deletions(-)
> > > > > > 
> > > > > > diff --git a/drivers/gpu/drm/i915/gvt/debugfs.c b/drivers/gpu/drm/i915/gvt/debugfs.c
> > > > > > index 03f081c3d9a4..baccbf1761b7 100644
> > > > > > --- a/drivers/gpu/drm/i915/gvt/debugfs.c
> > > > > > +++ b/drivers/gpu/drm/i915/gvt/debugfs.c
> > > > > > @@ -165,7 +165,7 @@ static int vgpu_status_get(void *data, u64 *val)
> > > > > >  	return 0;
> > > > > >  }
> > > > > >  
> > > > > > -DEFINE_SIMPLE_ATTRIBUTE(vgpu_status_fops, vgpu_status_get, NULL, "0x%llx\n");
> > > > > > +DEFINE_DEBUGFS_ATTRIBUTE(vgpu_status_fops, vgpu_status_get, NULL, "0x%llx\n");
> > > > > >  
> > > > > >  /**
> > > > > >   * intel_gvt_debugfs_add_vgpu - register debugfs entries for a vGPU
> > > > > > @@ -182,8 +182,8 @@ void intel_gvt_debugfs_add_vgpu(struct intel_vgpu *vgpu)
> > > > > >  			    &vgpu_mmio_diff_fops);
> > > > > >  	debugfs_create_file_unsafe("scan_nonprivbb", 0644, vgpu->debugfs, vgpu,
> > > > > >  				   &vgpu_scan_nonprivbb_fops);
> > > > > > -	debugfs_create_file("status", 0644, vgpu->debugfs, vgpu,
> > > > > > -			    &vgpu_status_fops);
> > > > > > +	debugfs_create_file_unsafe("status", 0644, vgpu->debugfs, vgpu,
> > > > > > +				   &vgpu_status_fops);
> > > > > >  }
> > > > > >  
> > > > > >  /**
> > > > > > -- 
> > > > > > 2.34.1
> > > > > > 
> > > > > > 
> > > > > > 
> > > 
> > > 
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Deepak R Varma <drv@mailo.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Praveen Kumar <kumarpraveen@linux.microsoft.com>,
	intel-gfx@lists.freedesktop.org,
	Saurabh Singh Sengar <ssengar@microsoft.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	intel-gvt-dev@lists.freedesktop.org,
	Zhi Wang <zhi.a.wang@intel.com>
Subject: Re: [PATCH 2/2] drm/i915/gvt: Avoid full proxy f_ops for vgpu_status debug attributes
Date: Wed, 11 Jan 2023 10:24:22 -0500	[thread overview]
Message-ID: <Y77UpjMG9t3SIkMo@intel.com> (raw)
In-Reply-To: <Y77SsDGaZ8+BjXel@ubun2204.myguest.virtualbox.org>

On Wed, Jan 11, 2023 at 08:46:00PM +0530, Deepak R Varma wrote:
> On Wed, Jan 11, 2023 at 10:00:11AM -0500, Rodrigo Vivi wrote:
> > > > Actually, could you please address the checkpatch issues before we can push?
> > > > Sorry about that, but just noticed now when I was going to push the other ones.
> > > 
> > > Hello Rodrigo,
> > > The checkpatch warning is associated with the long "make coccicheck ..." command
> > > in the commit message. It is not part of the code, so is should not be carried
> > > forward into the code base.
> > > If you still want me to correct it, I will need to split it into two lines which
> > > I think still violates the commit description guidelines.
> > 
> > This part I would just ignore or fix myself while merging. But the next one about
> > the parenthesis alignment need to be fixed in the code so we need another version.
> > Since we try to avoid touching the code between CI and merge.
> 
> I am sorry, but I am unable to locate the "second checkpatch complaint" you are
> referring to. I have received only the following from the checkpatch robot:
> 
> == Summary ==
> 
> Error: dim checkpatch failed
> 4c95e9b71212 drm/i915/gvt: Avoid full proxy f_ops for scan_nonprivbb debug attributes
> -:21: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
> #21:
> make coccicheck M=drivers/gpu/drm/i915/ MODE=patch COCCI=./scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci
> 
> total: 0 errors, 1 warnings, 0 checks, 22 lines checked
> 33d68a01cad3 drm/i915/gvt: Avoid full proxy f_ops for vgpu_status debug attributes
> -:21: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
> #21:
> make coccicheck M=drivers/gpu/drm/i915/ MODE=patch COCCI=./scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci
> 
> total: 0 errors, 1 warnings, 0 checks, 18 lines checked
> 

doh, my bad! this gvt patch is indeed right. up to gvt folks to modify this line
when merging or to ignore...

The problem I mentioned was in the other series. Sorry for the noise.

but for the record:

-:47: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#47: FILE: drivers/gpu/drm/i915/display/intel_drrs.c:386:
+	debugfs_create_file_unsafe("i915_drrs_ctl", 0644, crtc->base.debugfs_entry,
+				    crtc, &intel_drrs_debugfs_ctl_fops);


> ===============================
> 
> > 
> > Then, since you need to change that, while changing that, also please break
> > the coccinelle line in the commit msg.
> > 
> > I'd appreciate to have the patch for the pxp as well :)
> 
> Sure. As mentioned in the other thread, I am looking into it and would submit a
> patch accordingly.
> 
> Thank you,
> ./drv
> 
> > 
> > Thanks a lot,
> > Rodrigo.
> > 
> > 
> > > 
> > > Let me know what you think.
> > > 
> > > Thank you,
> > > ./drv
> > > 
> > > > 
> > > > > 
> > > > > > ---
> > > > > >  drivers/gpu/drm/i915/gvt/debugfs.c | 6 +++---
> > > > > >  1 file changed, 3 insertions(+), 3 deletions(-)
> > > > > > 
> > > > > > diff --git a/drivers/gpu/drm/i915/gvt/debugfs.c b/drivers/gpu/drm/i915/gvt/debugfs.c
> > > > > > index 03f081c3d9a4..baccbf1761b7 100644
> > > > > > --- a/drivers/gpu/drm/i915/gvt/debugfs.c
> > > > > > +++ b/drivers/gpu/drm/i915/gvt/debugfs.c
> > > > > > @@ -165,7 +165,7 @@ static int vgpu_status_get(void *data, u64 *val)
> > > > > >  	return 0;
> > > > > >  }
> > > > > >  
> > > > > > -DEFINE_SIMPLE_ATTRIBUTE(vgpu_status_fops, vgpu_status_get, NULL, "0x%llx\n");
> > > > > > +DEFINE_DEBUGFS_ATTRIBUTE(vgpu_status_fops, vgpu_status_get, NULL, "0x%llx\n");
> > > > > >  
> > > > > >  /**
> > > > > >   * intel_gvt_debugfs_add_vgpu - register debugfs entries for a vGPU
> > > > > > @@ -182,8 +182,8 @@ void intel_gvt_debugfs_add_vgpu(struct intel_vgpu *vgpu)
> > > > > >  			    &vgpu_mmio_diff_fops);
> > > > > >  	debugfs_create_file_unsafe("scan_nonprivbb", 0644, vgpu->debugfs, vgpu,
> > > > > >  				   &vgpu_scan_nonprivbb_fops);
> > > > > > -	debugfs_create_file("status", 0644, vgpu->debugfs, vgpu,
> > > > > > -			    &vgpu_status_fops);
> > > > > > +	debugfs_create_file_unsafe("status", 0644, vgpu->debugfs, vgpu,
> > > > > > +				   &vgpu_status_fops);
> > > > > >  }
> > > > > >  
> > > > > >  /**
> > > > > > -- 
> > > > > > 2.34.1
> > > > > > 
> > > > > > 
> > > > > > 
> > > 
> > > 
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Deepak R Varma <drv@mailo.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Praveen Kumar <kumarpraveen@linux.microsoft.com>,
	<intel-gfx@lists.freedesktop.org>,
	Saurabh Singh Sengar <ssengar@microsoft.com>,
	<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
	<intel-gvt-dev@lists.freedesktop.org>,
	Zhi Wang <zhi.a.wang@intel.com>
Subject: Re: [PATCH 2/2] drm/i915/gvt: Avoid full proxy f_ops for vgpu_status debug attributes
Date: Wed, 11 Jan 2023 10:24:22 -0500	[thread overview]
Message-ID: <Y77UpjMG9t3SIkMo@intel.com> (raw)
In-Reply-To: <Y77SsDGaZ8+BjXel@ubun2204.myguest.virtualbox.org>

On Wed, Jan 11, 2023 at 08:46:00PM +0530, Deepak R Varma wrote:
> On Wed, Jan 11, 2023 at 10:00:11AM -0500, Rodrigo Vivi wrote:
> > > > Actually, could you please address the checkpatch issues before we can push?
> > > > Sorry about that, but just noticed now when I was going to push the other ones.
> > > 
> > > Hello Rodrigo,
> > > The checkpatch warning is associated with the long "make coccicheck ..." command
> > > in the commit message. It is not part of the code, so is should not be carried
> > > forward into the code base.
> > > If you still want me to correct it, I will need to split it into two lines which
> > > I think still violates the commit description guidelines.
> > 
> > This part I would just ignore or fix myself while merging. But the next one about
> > the parenthesis alignment need to be fixed in the code so we need another version.
> > Since we try to avoid touching the code between CI and merge.
> 
> I am sorry, but I am unable to locate the "second checkpatch complaint" you are
> referring to. I have received only the following from the checkpatch robot:
> 
> == Summary ==
> 
> Error: dim checkpatch failed
> 4c95e9b71212 drm/i915/gvt: Avoid full proxy f_ops for scan_nonprivbb debug attributes
> -:21: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
> #21:
> make coccicheck M=drivers/gpu/drm/i915/ MODE=patch COCCI=./scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci
> 
> total: 0 errors, 1 warnings, 0 checks, 22 lines checked
> 33d68a01cad3 drm/i915/gvt: Avoid full proxy f_ops for vgpu_status debug attributes
> -:21: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
> #21:
> make coccicheck M=drivers/gpu/drm/i915/ MODE=patch COCCI=./scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci
> 
> total: 0 errors, 1 warnings, 0 checks, 18 lines checked
> 

doh, my bad! this gvt patch is indeed right. up to gvt folks to modify this line
when merging or to ignore...

The problem I mentioned was in the other series. Sorry for the noise.

but for the record:

-:47: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#47: FILE: drivers/gpu/drm/i915/display/intel_drrs.c:386:
+	debugfs_create_file_unsafe("i915_drrs_ctl", 0644, crtc->base.debugfs_entry,
+				    crtc, &intel_drrs_debugfs_ctl_fops);


> ===============================
> 
> > 
> > Then, since you need to change that, while changing that, also please break
> > the coccinelle line in the commit msg.
> > 
> > I'd appreciate to have the patch for the pxp as well :)
> 
> Sure. As mentioned in the other thread, I am looking into it and would submit a
> patch accordingly.
> 
> Thank you,
> ./drv
> 
> > 
> > Thanks a lot,
> > Rodrigo.
> > 
> > 
> > > 
> > > Let me know what you think.
> > > 
> > > Thank you,
> > > ./drv
> > > 
> > > > 
> > > > > 
> > > > > > ---
> > > > > >  drivers/gpu/drm/i915/gvt/debugfs.c | 6 +++---
> > > > > >  1 file changed, 3 insertions(+), 3 deletions(-)
> > > > > > 
> > > > > > diff --git a/drivers/gpu/drm/i915/gvt/debugfs.c b/drivers/gpu/drm/i915/gvt/debugfs.c
> > > > > > index 03f081c3d9a4..baccbf1761b7 100644
> > > > > > --- a/drivers/gpu/drm/i915/gvt/debugfs.c
> > > > > > +++ b/drivers/gpu/drm/i915/gvt/debugfs.c
> > > > > > @@ -165,7 +165,7 @@ static int vgpu_status_get(void *data, u64 *val)
> > > > > >  	return 0;
> > > > > >  }
> > > > > >  
> > > > > > -DEFINE_SIMPLE_ATTRIBUTE(vgpu_status_fops, vgpu_status_get, NULL, "0x%llx\n");
> > > > > > +DEFINE_DEBUGFS_ATTRIBUTE(vgpu_status_fops, vgpu_status_get, NULL, "0x%llx\n");
> > > > > >  
> > > > > >  /**
> > > > > >   * intel_gvt_debugfs_add_vgpu - register debugfs entries for a vGPU
> > > > > > @@ -182,8 +182,8 @@ void intel_gvt_debugfs_add_vgpu(struct intel_vgpu *vgpu)
> > > > > >  			    &vgpu_mmio_diff_fops);
> > > > > >  	debugfs_create_file_unsafe("scan_nonprivbb", 0644, vgpu->debugfs, vgpu,
> > > > > >  				   &vgpu_scan_nonprivbb_fops);
> > > > > > -	debugfs_create_file("status", 0644, vgpu->debugfs, vgpu,
> > > > > > -			    &vgpu_status_fops);
> > > > > > +	debugfs_create_file_unsafe("status", 0644, vgpu->debugfs, vgpu,
> > > > > > +				   &vgpu_status_fops);
> > > > > >  }
> > > > > >  
> > > > > >  /**
> > > > > > -- 
> > > > > > 2.34.1
> > > > > > 
> > > > > > 
> > > > > > 
> > > 
> > > 
> 
> 

  reply	other threads:[~2023-01-11 15:25 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 18:29 [Intel-gfx] [PATCH 0/2] drm/i915/gvt: Avoid full proxy f_ops debug attributes Deepak R Varma
2023-01-10 18:29 ` Deepak R Varma
2023-01-10 18:29 ` Deepak R Varma
2023-01-10 18:29 ` [Intel-gfx] [PATCH 1/2] drm/i915/gvt: Avoid full proxy f_ops for scan_nonprivbb " Deepak R Varma
2023-01-10 18:29   ` Deepak R Varma
2023-01-10 18:29   ` Deepak R Varma
2023-01-10 18:30 ` [Intel-gfx] [PATCH 2/2] drm/i915/gvt: Avoid full proxy f_ops for vgpu_status " Deepak R Varma
2023-01-10 18:30   ` Deepak R Varma
2023-01-10 18:30   ` Deepak R Varma
2023-01-10 18:49   ` [Intel-gfx] " Rodrigo Vivi
2023-01-10 18:49     ` Rodrigo Vivi
2023-01-10 18:49     ` Rodrigo Vivi
2023-01-11 10:02     ` [Intel-gfx] " Rodrigo Vivi
2023-01-11 10:02       ` Rodrigo Vivi
2023-01-11 10:02       ` Rodrigo Vivi
2023-01-11 14:53       ` [Intel-gfx] " Deepak R Varma
2023-01-11 14:53         ` Deepak R Varma
2023-01-11 14:53         ` Deepak R Varma
2023-01-11 15:00         ` [Intel-gfx] " Rodrigo Vivi
2023-01-11 15:00           ` Rodrigo Vivi
2023-01-11 15:00           ` Rodrigo Vivi
2023-01-11 15:16           ` [Intel-gfx] " Deepak R Varma
2023-01-11 15:16             ` Deepak R Varma
2023-01-11 15:16             ` Deepak R Varma
2023-01-11 15:24             ` Rodrigo Vivi [this message]
2023-01-11 15:24               ` Rodrigo Vivi
2023-01-11 15:24               ` Rodrigo Vivi
2023-01-16  5:44     ` [Intel-gfx] " Zhenyu Wang
2023-01-16  5:44       ` Zhenyu Wang
2023-01-16  5:44       ` Zhenyu Wang
2023-01-17 19:29       ` [Intel-gfx] " Rodrigo Vivi
2023-01-17 19:29         ` Rodrigo Vivi
2023-01-17 19:29         ` Rodrigo Vivi
2023-01-18  4:48         ` Deepak R Varma
2023-01-18  4:48           ` Deepak R Varma
2023-01-18  4:48           ` Deepak R Varma
2023-01-18 16:44           ` Rodrigo Vivi
2023-01-18 16:44             ` Rodrigo Vivi
2023-01-18 16:44             ` Rodrigo Vivi
2023-01-19  1:26             ` Zhenyu Wang
2023-01-19  1:26               ` Zhenyu Wang
2023-01-19  1:26               ` Zhenyu Wang
2023-01-19 22:05               ` Rodrigo Vivi
2023-01-19 22:05                 ` Rodrigo Vivi
2023-01-19 22:05                 ` Rodrigo Vivi
2023-01-20  2:20                 ` Zhenyu Wang
2023-01-20  2:20                   ` Zhenyu Wang
2023-01-20  2:20                   ` Zhenyu Wang
2023-01-10 21:54 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gvt: Avoid full proxy f_ops " Patchwork
2023-01-10 22:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-01-11  8:09 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=Y77UpjMG9t3SIkMo@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=drv@mailo.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=kumarpraveen@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ssengar@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.