From: Jani Nikula <jani.nikula@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Kevin Rogovin <kevin.rogovin@intel.com>
Subject: Re: [PATCH 0/1 RFC] Documentation patch for batchbuffer submission
Date: Mon, 19 Feb 2018 11:36:52 +0200 [thread overview]
Message-ID: <878tbpb9sb.fsf@intel.com> (raw)
In-Reply-To: <1518789862-4006-1-git-send-email-kevin.rogovin@intel.com>
On Fri, 16 Feb 2018, kevin.rogovin@intel.com wrote:
> From: Kevin Rogovin <kevin.rogovin@intel.com>
>
> This patch attempts to provide text for the kernel documentation on the
> subject of batchbuffer submission. The contents of the patch are essentially:
> - explain the nature of (PP)GTT and relocation with respect to GPU executing
> batchbuffers (as narrative) and
> - add a little more text on the implementation of batchbuffer submission
> (a little text and also including to i915.rst the already existing text
> in i915_gem_execbuffer.c).
That part belongs in the actual patch commit message.
BR,
Jani.
>
> In coming weeks I want to also provide documentation on the rules for handling
> the lists, the breadcumb jazz, locking rules to be followed in i915 and what
> the IRQ's handled by i915 end up triggering with respect to GEM.
>
> Comments (even flames) are welcome, especially for checking the truth to text
> written. I freely confess that I am using the act of writing the documentation
> to get myself deeply familiar with the way i915 GEM works.
>
> Any requests to write documentation for how GEM works I will gladly take up
> as well.
>
> Kevin Rogovin (1):
> drivers/gpu/drm/i915:Documentation for batchbuffer submission
>
> Documentation/gpu/i915.rst | 109 +++++++++++++++++++++++++++++
> drivers/gpu/drm/i915/i915_gem_execbuffer.c | 10 +++
> 2 files changed, 119 insertions(+)
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-02-19 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 14:04 [PATCH 0/1 RFC] Documentation patch for batchbuffer submission kevin.rogovin
2018-02-16 14:04 ` [PATCH 1/1 RFC] drivers/gpu/drm/i915:Documentation " kevin.rogovin
2018-02-19 13:38 ` Joonas Lahtinen
2018-02-27 6:58 ` Rogovin, Kevin
2018-02-16 14:10 ` ✗ Fi.CI.BAT: failure for Documentation patch " Patchwork
2018-02-19 9:36 ` Jani Nikula [this message]
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=878tbpb9sb.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kevin.rogovin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox