All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Zou, Nanhai" <nanhai.zou@intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
	"Anholt, Eric" <eric.anholt@intel.com>
Subject: Re: [PATCH 1/4] introduce intel_ring_buffer structure
Date: Fri, 14 May 2010 17:03:24 +0200	[thread overview]
Message-ID: <20100514150324.GE3413@viiv.ffwll.ch> (raw)
In-Reply-To: <20100514095114.GC3413@viiv.ffwll.ch>

Hi all,

On Fri, May 14, 2010 at 11:51:14AM +0200, Daniel Vetter wrote:
> So please explain the technical reasons we need this rather complex beast
> of code in the kernel?

Ok, I owe you my apologies (and a beer). I've read through the HD docs and
it looks like bsd decoding for avc/vc1 can't be done without the bsd
command stream. What a pain.

I'm currently crawling through the docs. It looks like we also need a new
gpu domain (something like I915_GEM_DOMAIN_BSD) in addition to a new
execution domain to properly support flushing and coherency. This way
round my concerns about userspace synchronization and the flush-both-rings
semantics would be void, too.

Yours, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2010-05-14 15:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  1:20 [PATCH 1/4] introduce intel_ring_buffer structure Zou Nan hai
2010-05-06  1:20 ` [PATCH 2/4] convert render engine to use intel_ring_buffer Zou Nan hai
2010-05-06  1:20 ` [PATCH 3/4] add BSD ring buffer support Zou Nan hai
2010-05-06  1:20 ` [PATCH 4/4] adapt intel_ring_buffer into gem Zou Nan hai
2010-05-07 21:34 ` [PATCH 1/4] introduce intel_ring_buffer structure Eric Anholt
2010-05-08 18:15   ` Thomas Bächler
2010-05-11 22:24 ` Daniel Vetter
2010-05-14  1:39   ` Zou, Nanhai
2010-05-14  9:51     ` Daniel Vetter
2010-05-14 15:03       ` Daniel Vetter [this message]
2010-05-17  1:59         ` Zou, Nanhai
2010-05-17 17:52           ` Daniel Vetter
2010-05-14 17:43     ` Owain Ainsworth
2010-05-17  1:43       ` Zou, Nanhai
2010-05-17 17:42         ` Daniel Vetter
2010-05-18  2:20           ` Zou, Nanhai
2010-05-18 16:19             ` Simon Farnsworth
2010-05-19  1:09               ` Zou, Nanhai
2010-05-19  9:00                 ` Simon Farnsworth
2010-05-19 16:54                   ` Eric Anholt
2010-05-19 17:33                     ` Simon Farnsworth
  -- strict thread matches above, loose matches on Subject: below --
2010-05-05  3:17 Zou Nan hai
2010-05-05 18:23 ` Daniel Vetter
2010-05-06  2:25   ` Zou, Nanhai

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=20100514150324.GE3413@viiv.ffwll.ch \
    --to=daniel@ffwll.ch \
    --cc=eric.anholt@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nanhai.zou@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.