public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <oushixiong@kylinos.cn>
To: "'Maxime Ripard'" <mripard@kernel.org>
Cc: "'Maarten Lankhorst'" <maarten.lankhorst@linux.intel.com>,
	"'Thomas Zimmermann'" <tzimmermann@suse.de>,
	"'David Airlie'" <airlied@gmail.com>,
	"'Daniel Vetter'" <daniel@ffwll.ch>,
	<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: 回复: [PATCH] drm/atomic-helper: Call stall_checks() before allocate drm_crtc_commit
Date: Mon, 6 Nov 2023 21:26:15 +0800	[thread overview]
Message-ID: <000301da10b4$d4e90690$7ebb13b0$@kylinos.cn> (raw)
In-Reply-To: <6yqalig6nvnlpt7loetugjdgp5z4w3qwhpqpzzsygffp5w32d6@guq6v3g2z7tq>

Hi,  
I think it will cause memory leaks if too many nonblock commit works return
-EBUSY.
You can try to send large number of nonblock commits by
drmModeAtomicCommit().

-----邮件原件-----
发件人: Maxime Ripard <mripard@kernel.org> 
发送时间: 2023年11月6日 18:33
收件人: oushixiong <oushixiong@kylinos.cn>
抄送: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>; Thomas
Zimmermann <tzimmermann@suse.de>; David Airlie <airlied@gmail.com>; Daniel
Vetter <daniel@ffwll.ch>; dri-devel@lists.freedesktop.org;
linux-kernel@vger.kernel.org
主题: Re: [PATCH] drm/atomic-helper: Call stall_checks() before allocate
drm_crtc_commit

Hi,

On Mon, Nov 06, 2023 at 03:37:42PM +0800, oushixiong wrote:
> From: Shixiong Ou <oushixiong@kylinos.cn>
> 
> Calling stall_checks() before allocating drm_crtc_commit not after that.
> 
> Signed-off-by: Shixiong Ou <oushixiong@kylinos.cn>

Generally speaking, we need much more context than that.

What bug did you encounter that makes you say that it should be moved?
How can we reproduce it? How long has that issue been in the code? What
makes you say that this is the right solution?

Maxime


  reply	other threads:[~2023-11-06 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06  7:37 [PATCH] drm/atomic-helper: Call stall_checks() before allocate drm_crtc_commit oushixiong
2023-11-06 10:32 ` Maxime Ripard
2023-11-06 13:26   ` oushixiong [this message]
2023-11-06 15:37     ` 回复: " 'Maxime Ripard'

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='000301da10b4$d4e90690$7ebb13b0$@kylinos.cn' \
    --to=oushixiong@kylinos.cn \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /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