From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Convert WARNs during userptr revoke to SIGBUS
Date: Fri, 9 Oct 2015 09:59:22 +0100 [thread overview]
Message-ID: <20151009085922.GI27939@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20151009085526.GO26718@phenom.ffwll.local>
On Fri, Oct 09, 2015 at 10:55:26AM +0200, Daniel Vetter wrote:
> On Fri, Oct 09, 2015 at 09:40:53AM +0100, Chris Wilson wrote:
> > On Fri, Oct 09, 2015 at 09:48:01AM +0200, Daniel Vetter wrote:
> > > On Thu, Oct 08, 2015 at 10:45:47AM +0100, Tvrtko Ursulin wrote:
> > > The concern is that this isn't how SIG_SEGV works, it's a signal the
> > > thread who made the invalid access gets directly. You never get a SIG_SEGV
> > > for bad access someone else has made. So essentially it's new ABI.
> >
> > SIGBUS. For which the answer is yes, you can and do get SIGBUS for
> > actions taken by other processes.
>
> Oh right I always forget that SIGBUS aliases with SIGIO. Anyway if
> userspace wants SIGIO we just need to provide it with a pollable fd and
> then it can use fcntl to make that happen. That's imo a much better api
> than unconditionally throwing around signals. Also we already have the
> reset stats ioctl to tell userspace that its gpu context is toats. If
> anyone wants that to be pollable (or even send SIGIO) I think we should
> extend that, with all the usual "needs userspace&igt" stuff on top.
It's not EIO handling, it is a SIGBUS in the canonical sense that the
backing storage for a mmap just vanished whilst you were using it.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-09 8:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 20:07 [PATCH] drm/i915: Convert WARNs during userptr revoke to SIGBUS Chris Wilson
2015-09-24 10:23 ` Tvrtko Ursulin
2015-09-24 10:31 ` Chris Wilson
2015-09-24 10:55 ` Tvrtko Ursulin
2015-09-28 13:42 ` Daniel Vetter
2015-09-28 13:52 ` Chris Wilson
2015-09-28 14:14 ` Daniel Vetter
2015-10-08 9:45 ` Tvrtko Ursulin
2015-10-09 7:48 ` Daniel Vetter
2015-10-09 8:40 ` Chris Wilson
2015-10-09 8:55 ` Daniel Vetter
2015-10-09 8:59 ` Chris Wilson [this message]
2015-10-09 9:03 ` Tvrtko Ursulin
2015-10-09 17:14 ` Daniel Vetter
2015-10-09 17:26 ` Chris Wilson
2015-10-09 18:33 ` Dave Gordon
2015-10-12 9:06 ` Tvrtko Ursulin
2015-10-12 9:31 ` Chris Wilson
2015-10-12 10:10 ` Chris Wilson
2015-10-12 12:59 ` Tvrtko Ursulin
2015-10-13 11:26 ` Daniel Vetter
2015-10-13 11:44 ` Chris Wilson
2015-10-13 12:23 ` Daniel Vetter
2015-10-13 13:09 ` Chris Wilson
2015-10-13 13:39 ` 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=20151009085922.GI27939@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@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 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.