From: Adam Jackson <ajax@redhat.com>
To: Ian Romanick <idr@freedesktop.org>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [RFC] GPU reset notification interface
Date: Wed, 18 Jul 2012 12:36:23 -0400 [thread overview]
Message-ID: <1342629383.3590.35.camel@atropine> (raw)
In-Reply-To: <5006E312.3010103@freedesktop.org>
[-- Attachment #1.1: Type: text/plain, Size: 696 bytes --]
On Wed, 2012-07-18 at 09:23 -0700, Ian Romanick wrote:
> On 07/18/2012 02:20 AM, Daniel Vetter wrote:
> > A few things:
> > - I agree with Chris that reset_in_progress should go, if userspace can
> > sneak in and witness a reset event, we have a bug in the kernel. Since
> > very recently, we actually have a few bugs less in that area ;-)
>
> I'm operating under the assumption that, from user space's perspective,
> resets are not instantaneous. If resets are instantaneous, that may
> change things.
Do they need to be instantaneous, or do they merely need to be
atomic-and-reasonably-quick? Could just block new ioctl submission
until the reset completes.
- ajax
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2012-07-18 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 22:16 [RFC] GPU reset notification interface Ian Romanick
2012-07-18 1:57 ` Ian Romanick
2012-07-18 7:06 ` Chris Wilson
2012-07-18 9:20 ` Daniel Vetter
2012-07-18 16:23 ` Ian Romanick
2012-07-18 16:36 ` Adam Jackson [this message]
2012-07-18 16:42 ` Daniel Vetter
2012-07-18 16:55 ` Daniel Vetter
2012-07-19 3:47 ` Ben Widawsky
2012-07-19 15:58 ` Ian Romanick
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=1342629383.3590.35.camel@atropine \
--to=ajax@redhat.com \
--cc=idr@freedesktop.org \
--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.