From: Dave Airlie <airlied@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Matthew Brost <matthew.brost@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
carl.zhang@intel.com, Jason Ekstrand <jason.ekstrand@intel.com>,
mesa-dev <mesa-dev@lists.freedesktop.org>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
"Koenig, Christian" <christian.koenig@amd.com>
Subject: Re: [Mesa-dev] [Intel-gfx] [RFC PATCH 1/2] drm/doc/rfc: i915 GuC submission / DRM scheduler
Date: Sat, 5 Jun 2021 05:48:23 +1000 [thread overview]
Message-ID: <CAPM=9twjUGfXE9bXLap=tyDnKqxP5JXquNR-rO-Zuj05Uv=v9A@mail.gmail.com> (raw)
In-Reply-To: <YLplVgu7y8fzaFF0@phenom.ffwll.local>
On Sat, 5 Jun 2021 at 03:39, Daniel Vetter <daniel@ffwll.ch> wrote:
>
> On Wed, May 26, 2021 at 04:33:56PM -0700, Matthew Brost wrote:
> > Add entry for i915 GuC submission / DRM scheduler integration plan.
> > Follow up patch with details of new parallel submission uAPI to come.
> >
> > v2:
> > (Daniel Vetter)
> > - Expand explaination of why bonding isn't supported for GuC
> > submission
> > - CC some of the DRM scheduler maintainers
> > - Add priority inheritance / boosting use case
> > - Add reasoning for removing in order assumptions
> > (Daniel Stone)
> > - Add links to priority spec
> >
> > Cc: Christian König <christian.koenig@amd.com>
> > Cc: Luben Tuikov <luben.tuikov@amd.com>
> > Cc: Alex Deucher <alexander.deucher@amd.com>
> > Cc: Steven Price <steven.price@arm.com>
> > Cc: Jon Bloomfield <jon.bloomfield@intel.com>
> > Cc: Jason Ekstrand <jason@jlekstrand.net>
> > Cc: Dave Airlie <airlied@gmail.com>
> > Cc: Daniel Vetter <daniel.vetter@intel.com>
> > Cc: Jason Ekstrand <jason@jlekstrand.net>
> > Cc: dri-devel@lists.freedesktop.org
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
>
> You have a one-line hunk in the next patch that probably should be here.
> With that moved.
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Acked-by: Dave Airlie <airlied@redhat.com>
And yes having the todos for GuC tracked would be good externally, so
pressure can be applied for new fw releases with those features.
Dave.
next prev parent reply other threads:[~2021-06-04 19:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 23:33 [RFC PATCH 0/2] GuC submission / DRM scheduler integration plan + new uAPI Matthew Brost
2021-05-26 23:33 ` [RFC PATCH 1/2] drm/doc/rfc: i915 GuC submission / DRM scheduler Matthew Brost
2021-05-27 10:06 ` [Intel-gfx] " Tvrtko Ursulin
2021-05-27 11:24 ` Daniel Vetter
2021-06-04 17:39 ` Daniel Vetter
2021-06-04 19:48 ` Dave Airlie [this message]
2021-05-26 23:33 ` [RFC PATCH 2/2] drm/doc/rfc: i915 new parallel submission uAPI plan Matthew Brost
2021-05-27 15:01 ` [Intel-gfx] " Tvrtko Ursulin
2021-06-04 17:59 ` Daniel Vetter
2021-06-11 19:50 ` Matthew Brost
2021-06-17 16:46 ` Daniel Vetter
2021-06-17 17:27 ` Matthew Brost
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='CAPM=9twjUGfXE9bXLap=tyDnKqxP5JXquNR-rO-Zuj05Uv=v9A@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=carl.zhang@intel.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jason.ekstrand@intel.com \
--cc=matthew.brost@intel.com \
--cc=mesa-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).