All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deepak R Varma <drv@mailo.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
	Zhi Wang <zhi.a.wang@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	intel-gvt-dev@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Cc: Praveen Kumar <kumarpraveen@linux.microsoft.com>,
	Saurabh Singh Sengar <ssengar@microsoft.com>
Subject: [Intel-gfx] [PATCH 0/2] drm/i915/gvt: Avoid full proxy f_ops debug attributes
Date: Tue, 10 Jan 2023 23:59:12 +0530	[thread overview]
Message-ID: <cover.1673375066.git.drv@mailo.com> (raw)

This patch series proposes to replace a combination of DEFINE_SIMPLE_ATTRIBUTE() +
debugfs_create_file() by a combination of DEFINE_DEBUGFS_ATTRIBUTE() +
debugfs_create_file_unsafe(). The change reduced overhead in terms of managing
the full proxy f_ops at runtime. The patches 1 & 2 covers for the scan_nonprivbb
 and vgpu_status f_ops debugfs attributes respectively.

Following coccicheck make command helped identify this change:
    
make coccicheck M=drivers/gpu/drm/i915/ MODE=patch COCCI=./scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci



Deepak R Varma (2):
  drm/i915/gvt: Avoid full proxy f_ops for scan_nonprivbb debug
    attributes
  drm/i915/gvt: Avoid full proxy f_ops for vgpu_status debug attributes

 drivers/gpu/drm/i915/gvt/debugfs.c | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

-- 
2.34.1




WARNING: multiple messages have this Message-ID (diff)
From: Deepak R Varma <drv@mailo.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
	Zhi Wang <zhi.a.wang@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	intel-gvt-dev@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Cc: Praveen Kumar <kumarpraveen@linux.microsoft.com>,
	Saurabh Singh Sengar <ssengar@microsoft.com>
Subject: [PATCH 0/2] drm/i915/gvt: Avoid full proxy f_ops debug attributes
Date: Tue, 10 Jan 2023 23:59:12 +0530	[thread overview]
Message-ID: <cover.1673375066.git.drv@mailo.com> (raw)

This patch series proposes to replace a combination of DEFINE_SIMPLE_ATTRIBUTE() +
debugfs_create_file() by a combination of DEFINE_DEBUGFS_ATTRIBUTE() +
debugfs_create_file_unsafe(). The change reduced overhead in terms of managing
the full proxy f_ops at runtime. The patches 1 & 2 covers for the scan_nonprivbb
 and vgpu_status f_ops debugfs attributes respectively.

Following coccicheck make command helped identify this change:
    
make coccicheck M=drivers/gpu/drm/i915/ MODE=patch COCCI=./scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci



Deepak R Varma (2):
  drm/i915/gvt: Avoid full proxy f_ops for scan_nonprivbb debug
    attributes
  drm/i915/gvt: Avoid full proxy f_ops for vgpu_status debug attributes

 drivers/gpu/drm/i915/gvt/debugfs.c | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

-- 
2.34.1




WARNING: multiple messages have this Message-ID (diff)
From: Deepak R Varma <drv@mailo.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
	Zhi Wang <zhi.a.wang@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	intel-gvt-dev@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Cc: Saurabh Singh Sengar <ssengar@microsoft.com>,
	Praveen Kumar <kumarpraveen@linux.microsoft.com>
Subject: [PATCH 0/2] drm/i915/gvt: Avoid full proxy f_ops debug attributes
Date: Tue, 10 Jan 2023 23:59:12 +0530	[thread overview]
Message-ID: <cover.1673375066.git.drv@mailo.com> (raw)

This patch series proposes to replace a combination of DEFINE_SIMPLE_ATTRIBUTE() +
debugfs_create_file() by a combination of DEFINE_DEBUGFS_ATTRIBUTE() +
debugfs_create_file_unsafe(). The change reduced overhead in terms of managing
the full proxy f_ops at runtime. The patches 1 & 2 covers for the scan_nonprivbb
 and vgpu_status f_ops debugfs attributes respectively.

Following coccicheck make command helped identify this change:
    
make coccicheck M=drivers/gpu/drm/i915/ MODE=patch COCCI=./scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci



Deepak R Varma (2):
  drm/i915/gvt: Avoid full proxy f_ops for scan_nonprivbb debug
    attributes
  drm/i915/gvt: Avoid full proxy f_ops for vgpu_status debug attributes

 drivers/gpu/drm/i915/gvt/debugfs.c | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

-- 
2.34.1




             reply	other threads:[~2023-01-10 18:29 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 18:29 Deepak R Varma [this message]
2023-01-10 18:29 ` [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 ` [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             ` [Intel-gfx] " Rodrigo Vivi
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=cover.1673375066.git.drv@mailo.com \
    --to=drv@mailo.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=kumarpraveen@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=ssengar@microsoft.com \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhi.a.wang@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 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.