From: Takashi Iwai <tiwai@suse.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/fb-helper: Don't call dirty callback for untouched clips
Date: Tue, 25 Oct 2016 10:17:47 +0200 [thread overview]
Message-ID: <s5hoa28n8pg.wl-tiwai@suse.de> (raw)
In-Reply-To: <20161025080930.2wnshqm274mf4m5k@phenom.ffwll.local>
On Tue, 25 Oct 2016 10:09:30 +0200,
Daniel Vetter wrote:
>
> On Tue, Oct 25, 2016 at 08:46:28AM +0200, Takashi Iwai wrote:
> > On Fri, 21 Oct 2016 14:52:07 +0200,
> > Ville Syrjälä wrote:
> > >
> > > On Thu, Oct 20, 2016 at 05:05:30PM +0200, Takashi Iwai wrote:
> > > > Since 4.7 kernel, we've seen the error messages like
> > > >
> > > > kernel: [TTM] Buffer eviction failed
> > > > kernel: qxl 0000:00:02.0: object_init failed for (4026540032, 0x00000001)
> > > > kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
> > > >
> > > > on QXL when switching and accessing on VT. The culprit was the
> > > > generic deferred_io code (qxl driver switched to it since 4.7).
> > > > There is a race between the dirty clip update and the call of
> > > > callback.
> > > >
> > > > In drm_fb_helper_dirty(), the dirty clip is updated in the spinlock,
> > > > while it kicks off the update worker outside the spinlock. Meanwhile
> > > > the update worker clears the dirty clip in the spinlock, too. Thus,
> > > > when drm_fb_helper_dirty() is called concurrently, schedule_work() is
> > > > called after the clip is cleared in the first worker call.
> > > >
> > > > This patch addresses it by validating the clip before calling the
> > > > dirty fb callback.
> > > >
> > > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98322
> > > > Bugzilla: https://bugzilla.suse.com/show_bug.cgi?id=1003298
> > > > Fixes: eaa434defaca ('drm/fb-helper: Add fb_deferred_io support')
> > > > Cc: <stable@vger.kernel.org>
> > > > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > >
> > > Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Daniel, could you pick this if it's OK as a quick fix? Currently
> > qxl driver is utterly broken, and we should recover it ASAP. On top
> > of this, we can put a more comprehensive fix covering both this and
> > dirtyfb ioctl code paths.
>
> I thought I've pinged Dave already to pick up, I'll poke him again.
Thanks!
Takashi
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Noralf Trønnes" <noralf@tronnes.org>,
"David Airlie" <airlied@linux.ie>
Subject: Re: [PATCH v2] drm/fb-helper: Don't call dirty callback for untouched clips
Date: Tue, 25 Oct 2016 10:17:47 +0200 [thread overview]
Message-ID: <s5hoa28n8pg.wl-tiwai@suse.de> (raw)
In-Reply-To: <20161025080930.2wnshqm274mf4m5k@phenom.ffwll.local>
On Tue, 25 Oct 2016 10:09:30 +0200,
Daniel Vetter wrote:
>
> On Tue, Oct 25, 2016 at 08:46:28AM +0200, Takashi Iwai wrote:
> > On Fri, 21 Oct 2016 14:52:07 +0200,
> > Ville Syrjälä wrote:
> > >
> > > On Thu, Oct 20, 2016 at 05:05:30PM +0200, Takashi Iwai wrote:
> > > > Since 4.7 kernel, we've seen the error messages like
> > > >
> > > > kernel: [TTM] Buffer eviction failed
> > > > kernel: qxl 0000:00:02.0: object_init failed for (4026540032, 0x00000001)
> > > > kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
> > > >
> > > > on QXL when switching and accessing on VT. The culprit was the
> > > > generic deferred_io code (qxl driver switched to it since 4.7).
> > > > There is a race between the dirty clip update and the call of
> > > > callback.
> > > >
> > > > In drm_fb_helper_dirty(), the dirty clip is updated in the spinlock,
> > > > while it kicks off the update worker outside the spinlock. Meanwhile
> > > > the update worker clears the dirty clip in the spinlock, too. Thus,
> > > > when drm_fb_helper_dirty() is called concurrently, schedule_work() is
> > > > called after the clip is cleared in the first worker call.
> > > >
> > > > This patch addresses it by validating the clip before calling the
> > > > dirty fb callback.
> > > >
> > > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98322
> > > > Bugzilla: https://bugzilla.suse.com/show_bug.cgi?id=1003298
> > > > Fixes: eaa434defaca ('drm/fb-helper: Add fb_deferred_io support')
> > > > Cc: <stable@vger.kernel.org>
> > > > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > >
> > > Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Daniel, could you pick this if it's OK as a quick fix? Currently
> > qxl driver is utterly broken, and we should recover it ASAP. On top
> > of this, we can put a more comprehensive fix covering both this and
> > dirtyfb ioctl code paths.
>
> I thought I've pinged Dave already to pick up, I'll poke him again.
Thanks!
Takashi
next prev parent reply other threads:[~2016-10-25 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 15:05 [PATCH v2] drm/fb-helper: Don't call dirty callback for untouched clips Takashi Iwai
2016-10-21 12:52 ` Ville Syrjälä
2016-10-21 12:52 ` Ville Syrjälä
2016-10-25 6:46 ` Takashi Iwai
2016-10-25 8:09 ` Daniel Vetter
2016-10-25 8:17 ` Takashi Iwai [this message]
2016-10-25 8:17 ` Takashi Iwai
2016-10-26 8:32 ` Daniel Vetter
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=s5hoa28n8pg.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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.