From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
Mika Kuoppala <mika.kuoppala@linux.intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH RFC 3/4] drm/i915: add SVM execbuf ioctl v10
Date: Wed, 17 Aug 2016 12:37:40 +0300 [thread overview]
Message-ID: <1471426660.3613.24.camel@linux.intel.com> (raw)
In-Reply-To: <1471278414.2982.6.camel@virtuousgeek.org>
On ma, 2016-08-15 at 09:26 -0700, Jesse Barnes wrote:
> On Mon, 2016-08-15 at 15:34 +0300, Mika Kuoppala wrote:
> >
> > No idea yet why we would need to limit for rcs only.
> >
> I went back and forth; I think I did test on the BLT ring and maybe one
> of the video rings and things worked on at least one platform. But I'm
> still worried about bugs...
>
Any other reason for worrying other than lack of testing?
I'm pretty sure programs using OpenCL (Beignet) will want this on other
rings too for zero-copy video processing as an example.
Regards, Joonas
> Jesse
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-17 9:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 11:48 [PATCH RFC 0/4] svm support Mika Kuoppala
2016-08-15 11:48 ` [PATCH RFC 1/4] drm/i915: add create_context2 ioctl Mika Kuoppala
2016-08-15 11:55 ` Chris Wilson
2016-08-15 12:25 ` Mika Kuoppala
2016-08-15 12:56 ` Chris Wilson
2016-08-15 16:25 ` Jesse Barnes
2016-08-15 16:36 ` Chris Wilson
2016-08-15 12:03 ` Joonas Lahtinen
2016-08-15 11:48 ` [PATCH RFC 2/4] drm/i915: IOMMU based SVM implementation v13 Mika Kuoppala
2016-08-15 12:05 ` Chris Wilson
2016-08-15 12:13 ` David Woodhouse
2016-08-15 12:23 ` Chris Wilson
2016-08-15 12:30 ` David Woodhouse
2016-08-15 12:53 ` Chris Wilson
2016-08-15 13:04 ` David Woodhouse
2016-08-15 12:07 ` David Woodhouse
2016-08-15 11:48 ` [PATCH RFC 3/4] drm/i915: add SVM execbuf ioctl v10 Mika Kuoppala
2016-08-15 12:09 ` Chris Wilson
2016-08-15 12:34 ` Mika Kuoppala
2016-08-15 16:26 ` Jesse Barnes
2016-08-17 9:37 ` Joonas Lahtinen [this message]
2016-08-17 14:59 ` Jesse Barnes
2016-08-15 11:48 ` [PATCH RFC 4/4] drm/i915: Add param for SVM Mika Kuoppala
2016-08-15 12:11 ` Chris Wilson
2016-08-15 12:22 ` Mika Kuoppala
2016-08-15 12:24 ` ✗ Ro.CI.BAT: failure for svm support Patchwork
2016-08-15 13:43 ` [PATCH RFC 0/4] " Chris Wilson
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=1471426660.3613.24.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=mika.kuoppala@linux.intel.com \
/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.