[pull] amdgpu, amdkfd drm-next-5.3

Daniel Vetter daniel.vetter at ffwll.ch
Tue Jun 4 16:46:44 UTC 2019


On Tue, Jun 4, 2019 at 4:46 PM Alex Deucher <alexdeucher at gmail.com> wrote:
>
> On Mon, Jun 3, 2019 at 11:36 AM Daniel Vetter <daniel.vetter at ffwll.ch> wrote:
> >
> > On Thu, May 30, 2019 at 12:09 AM Alex Deucher <alexdeucher at gmail.com> wrote:
> > >
> > > Hi Dave, Daniel,
> > >
> > > New stuff for 5.3:
> > > - Add new thermal sensors for vega asics
> > > - Various RAS fixes
> > > - Add sysfs interface for memory interface utilization
> > > - Use HMM rather than mmu notifier for user pages
> > > - Expose xgmi topology via kfd
> > > - SR-IOV fixes
> > > - Fixes for manual driver reload
> > > - Add unique identifier for vega asics
> > > - Clean up user fence handling with UVD/VCE/VCN blocks
> > > - Convert DC to use core bpc attribute rather than a custom one
> > > - Add GWS support for KFD
> > > - Vega powerplay improvements
> > > - Add CRC support for DCE 12
> > > - SR-IOV support for new security policy
> > > - Various cleanups
> >
> > > Chunming Zhou (1):
> > >       drm/amdgpu: add DRIVER_SYNCOBJ_TIMELINE to amdgpu
> >
> > This unconditionally enables timeline syncobj support, Which I thought
> > we've decided to hold back behind some module_param_named_unsafe or
> > experimental Kconfig, at least until KHR ratifies the extensions and
> > everyone can publish the mesa patches. This is kinda uapi without
> > userspace as-is ... also not on your summary, or I'm blind.
>
> Sorry, for some reason I had it in my head that we were going to start
> enabling this is 5.3.  Maybe I was mixing it up with something else.
> I need to re-read the thread.  I can send an updated pull with a
> revert.

Yeah I think the idea was to get this in, but somewhere hidden until
it's released by khr. I think Kconfig/module option/ifdef or just not
yet merging the patch with the driver flag where discussed. Last one I
think is what Lionel plans to do for i915. Dave already merged your
pull, but it's -next and far from merge window so totally fine if you
only take care of this on the next regular feature pull imo.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch


More information about the dri-devel mailing list