From: Dave Airlie <airlied@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: add gem/gt TODO
Date: Wed, 24 Mar 2021 16:34:46 +1000 [thread overview]
Message-ID: <CAPM=9tyi3g_8hMPkGK+fSoMPxR-w6EzCh9iJpy4m1gCFb2z5Hg@mail.gmail.com> (raw)
In-Reply-To: <YFnqYj3geFFLFJac@phenom.ffwll.local>
On Tue, 23 Mar 2021 at 23:17, Daniel Vetter <daniel@ffwll.ch> wrote:
>
> On Tue, Mar 23, 2021 at 09:44:52AM +0100, Daniel Vetter wrote:
> > We've discussed a bit how to get the gem/gt team better integrated
> > and collaborate more with the wider community and agreed to the
> > following:
> >
> > - all gem/gt patches are reviewed on dri-devel for now. That's
> > overkill, but in the past there was definitely too little of that.
> >
> > - i915-gem folks are encouraged to cross review core patches from
> > other teams
> >
> > - big features (especially uapi changes) need to be discussed in an
> > rfc patch that documents the interface and big picture design,
> > before we get lost in the details of the code
> >
> > - Also a rough TODO (can be refined as we go ofc) to get gem/gt back
> > on track, like we've e.g. done with DAL/DC to get that in shape.
I think we mentioned in the past about having better annotations for
dma_fence critical sections,
Otherwise I think this is a great list to get us out of the woods and
seeing how to move forward again.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Dave Airlie <airlied@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: add gem/gt TODO
Date: Wed, 24 Mar 2021 16:34:46 +1000 [thread overview]
Message-ID: <CAPM=9tyi3g_8hMPkGK+fSoMPxR-w6EzCh9iJpy4m1gCFb2z5Hg@mail.gmail.com> (raw)
In-Reply-To: <YFnqYj3geFFLFJac@phenom.ffwll.local>
On Tue, 23 Mar 2021 at 23:17, Daniel Vetter <daniel@ffwll.ch> wrote:
>
> On Tue, Mar 23, 2021 at 09:44:52AM +0100, Daniel Vetter wrote:
> > We've discussed a bit how to get the gem/gt team better integrated
> > and collaborate more with the wider community and agreed to the
> > following:
> >
> > - all gem/gt patches are reviewed on dri-devel for now. That's
> > overkill, but in the past there was definitely too little of that.
> >
> > - i915-gem folks are encouraged to cross review core patches from
> > other teams
> >
> > - big features (especially uapi changes) need to be discussed in an
> > rfc patch that documents the interface and big picture design,
> > before we get lost in the details of the code
> >
> > - Also a rough TODO (can be refined as we go ofc) to get gem/gt back
> > on track, like we've e.g. done with DAL/DC to get that in shape.
I think we mentioned in the past about having better annotations for
dma_fence critical sections,
Otherwise I think this is a great list to get us out of the woods and
seeing how to move forward again.
Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-03-24 6:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 8:44 [PATCH 1/2] drm/i915: add gem/gt TODO Daniel Vetter
2021-03-23 8:44 ` [Intel-gfx] " Daniel Vetter
2021-03-23 8:44 ` [PATCH 2/2] drm/doc: Add RFC section Daniel Vetter
2021-03-23 8:44 ` [Intel-gfx] " Daniel Vetter
2021-03-23 12:37 ` Rodrigo Vivi
2021-03-23 12:37 ` [Intel-gfx] " Rodrigo Vivi
2021-03-23 13:10 ` Daniel Vetter
2021-03-23 13:10 ` [Intel-gfx] " Daniel Vetter
2021-03-23 13:38 ` Rodrigo Vivi
2021-03-23 13:38 ` [Intel-gfx] " Rodrigo Vivi
2021-03-23 17:01 ` Simon Ser
2021-03-23 17:01 ` [Intel-gfx] " Simon Ser
2021-03-23 17:55 ` Jason Ekstrand
2021-03-23 17:55 ` [Intel-gfx] " Jason Ekstrand
2021-03-23 18:31 ` Daniel Vetter
2021-03-23 18:31 ` [Intel-gfx] " Daniel Vetter
2021-03-24 6:32 ` Dave Airlie
2021-03-24 6:32 ` Dave Airlie
2021-03-23 9:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915: add gem/gt TODO Patchwork
2021-03-23 9:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-03-23 10:13 ` [PATCH 1/2] " Jani Nikula
2021-03-23 10:13 ` [Intel-gfx] " Jani Nikula
2021-03-23 11:57 ` Daniel Vetter
2021-03-23 11:57 ` [Intel-gfx] " Daniel Vetter
2021-03-23 12:34 ` Rodrigo Vivi
2021-03-23 12:34 ` [Intel-gfx] " Rodrigo Vivi
2021-03-23 13:18 ` Daniel Vetter
2021-03-23 13:18 ` [Intel-gfx] " Daniel Vetter
2021-03-23 18:07 ` Jason Ekstrand
2021-03-23 18:07 ` [Intel-gfx] " Jason Ekstrand
2021-03-23 13:17 ` Daniel Vetter
2021-03-23 13:17 ` [Intel-gfx] " Daniel Vetter
2021-03-24 6:34 ` Dave Airlie [this message]
2021-03-24 6:34 ` Dave Airlie
2021-03-24 2:29 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] " Patchwork
2021-03-24 21:10 [Intel-gfx] [PATCH 1/2] " Daniel Vetter
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=9tyi3g_8hMPkGK+fSoMPxR-w6EzCh9iJpy4m1gCFb2z5Hg@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.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.