From: "Anton V. Boyarshinov" <boyarsh@altlinux.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] xf86drm.c: add counter for ioctl restarting
Date: Mon, 16 Apr 2012 12:45:40 +0400 [thread overview]
Message-ID: <20120416124540.5de0b8c2@boyarsh.office.altlinux.ru> (raw)
In-Reply-To: <1334324469_408990@CP5-2952>
Hello
> > It seems, that limiting ioctl restarting by some resonable number of trys
> > is a dirty but working way to prevent Xorg lockups.
>
> And you have audited all callpaths to make sure that they can handle
> EINTR? Up until now it was part of the libdrm api that it did not return
> EINTR...
Speaking strictly no but this code works fine on my Nvidia ION box
with nouveau about a 4 monthes without user-visible problems. It also
have some logging code that shows that all ioctls which have been
restarted more then 5 times are restarting forewer (actually 100
times), but this logging code really unpstreamable.
> From my naive pov, we could just fix the root cause of the bug rather
> than escalating the bug into a random failure.
Yes. This is a dirty trick. But from the user scope, Xorg lockup is a
nasty thing. I have some lockups in a day a year ago, then some bugs
was fixed and a have some lockups in a week. Better, but not so good.
With this patch i have no lockups.
And, from the other side, this patch can be a tool for finding real
bugs if someone add proper logging to if (i don't know the right way to
log problems from libdrm) with ioctl, parameters and restart count.
Users will be able to add this informaition to the bugreports without
accessing by network to locked box.
Regards
Anton
next prev parent reply other threads:[~2012-04-16 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 13:26 [PATCH] xf86drm.c: add counter for ioctl restarting Anton V. Boyarshinov
2012-04-13 13:40 ` Chris Wilson
2012-04-16 8:45 ` Anton V. Boyarshinov [this message]
2012-04-13 13:42 ` Daniel Vetter
2012-04-13 14:45 ` Ville Syrjälä
2012-04-16 8:54 ` Anton V. Boyarshinov
2012-04-16 14:12 ` Adam Jackson
2012-04-16 15:05 ` Anton V. Boyarshinov
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=20120416124540.5de0b8c2@boyarsh.office.altlinux.ru \
--to=boyarsh@altlinux.org \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox