From: Zhenneng Li <lizhenneng@kylinos.cn>
To: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: 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>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Zhenneng Li <lizhenneng@kylinos.cn>
Subject: [PATCH] drm/i915: remove unnecessary spin_lock_irq
Date: Fri, 29 Apr 2022 12:03:55 +0800 [thread overview]
Message-ID: <20220429040355.2644322-1-lizhenneng@kylinos.cn> (raw)
This code will not be called by interrupt handler,
so change it to spin_lock.
Signed-off-by: Zhenneng Li <lizhenneng@kylinos.cn>
---
drivers/gpu/drm/i915/i915_scheduler.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_scheduler.c b/drivers/gpu/drm/i915/i915_scheduler.c
index 762127dd56c5..6615102a1568 100644
--- a/drivers/gpu/drm/i915/i915_scheduler.c
+++ b/drivers/gpu/drm/i915/i915_scheduler.c
@@ -288,9 +288,9 @@ static void __i915_schedule(struct i915_sched_node *node,
void i915_schedule(struct i915_request *rq, const struct i915_sched_attr *attr)
{
- spin_lock_irq(&schedule_lock);
+ spin_lock(&schedule_lock);
__i915_schedule(&rq->sched, attr);
- spin_unlock_irq(&schedule_lock);
+ spin_unlock(&schedule_lock);
}
void i915_sched_node_init(struct i915_sched_node *node)
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Zhenneng Li <lizhenneng@kylinos.cn>
To: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Zhenneng Li <lizhenneng@kylinos.cn>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH] drm/i915: remove unnecessary spin_lock_irq
Date: Fri, 29 Apr 2022 12:03:55 +0800 [thread overview]
Message-ID: <20220429040355.2644322-1-lizhenneng@kylinos.cn> (raw)
This code will not be called by interrupt handler,
so change it to spin_lock.
Signed-off-by: Zhenneng Li <lizhenneng@kylinos.cn>
---
drivers/gpu/drm/i915/i915_scheduler.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_scheduler.c b/drivers/gpu/drm/i915/i915_scheduler.c
index 762127dd56c5..6615102a1568 100644
--- a/drivers/gpu/drm/i915/i915_scheduler.c
+++ b/drivers/gpu/drm/i915/i915_scheduler.c
@@ -288,9 +288,9 @@ static void __i915_schedule(struct i915_sched_node *node,
void i915_schedule(struct i915_request *rq, const struct i915_sched_attr *attr)
{
- spin_lock_irq(&schedule_lock);
+ spin_lock(&schedule_lock);
__i915_schedule(&rq->sched, attr);
- spin_unlock_irq(&schedule_lock);
+ spin_unlock(&schedule_lock);
}
void i915_sched_node_init(struct i915_sched_node *node)
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Zhenneng Li <lizhenneng@kylinos.cn>
To: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Zhenneng Li <lizhenneng@kylinos.cn>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-gfx] [PATCH] drm/i915: remove unnecessary spin_lock_irq
Date: Fri, 29 Apr 2022 12:03:55 +0800 [thread overview]
Message-ID: <20220429040355.2644322-1-lizhenneng@kylinos.cn> (raw)
This code will not be called by interrupt handler,
so change it to spin_lock.
Signed-off-by: Zhenneng Li <lizhenneng@kylinos.cn>
---
drivers/gpu/drm/i915/i915_scheduler.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_scheduler.c b/drivers/gpu/drm/i915/i915_scheduler.c
index 762127dd56c5..6615102a1568 100644
--- a/drivers/gpu/drm/i915/i915_scheduler.c
+++ b/drivers/gpu/drm/i915/i915_scheduler.c
@@ -288,9 +288,9 @@ static void __i915_schedule(struct i915_sched_node *node,
void i915_schedule(struct i915_request *rq, const struct i915_sched_attr *attr)
{
- spin_lock_irq(&schedule_lock);
+ spin_lock(&schedule_lock);
__i915_schedule(&rq->sched, attr);
- spin_unlock_irq(&schedule_lock);
+ spin_unlock(&schedule_lock);
}
void i915_sched_node_init(struct i915_sched_node *node)
--
2.25.1
next reply other threads:[~2022-04-29 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 4:03 Zhenneng Li [this message]
2022-04-29 4:03 ` [Intel-gfx] [PATCH] drm/i915: remove unnecessary spin_lock_irq Zhenneng Li
2022-04-29 4:03 ` Zhenneng Li
2022-04-29 17:19 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " 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=20220429040355.2644322-1-lizhenneng@kylinos.cn \
--to=lizhenneng@kylinos.cn \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.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.