dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: "Liu, Monk" <Monk.Liu-5C7GfCeVMHo@public.gmane.org>,
	"Koenig,
	Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org>,
	"Deucher,
	Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>
Cc: "Grodzovsky,
	Andrey" <Andrey.Grodzovsky-5C7GfCeVMHo@public.gmane.org>,
	David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
	"dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	"patchwork-lst-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org"
	<patchwork-lst-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	"kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org"
	<kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: Re: [PATCH 0/2] Move scheduler out of AMDGPU
Date: Mon, 04 Dec 2017 10:42:53 +0100	[thread overview]
Message-ID: <1512380573.6394.1.camel@pengutronix.de> (raw)
In-Reply-To: <BLUPR12MB04491E836AFBE4759784405E843E0-7LeqcoF/hwpTIQvHjXdJlwdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>

Hi,

Am Samstag, den 02.12.2017, 12:14 +0000 schrieb Liu, Monk:
> I'm wondering if GPU reset still work after this home move ...

Why wouldn't it continue to work? After all this is just a code move
that doesn't change anything about the inner workings of the scheduler.

Regards,
Lucas

> 
> -----Original Message-----
> From: amd-gfx [mailto:amd-gfx-bounces@lists.freedesktop.org] On
> Behalf Of Christian K?nig
> Sent: Friday, December 1, 2017 11:55 PM
> To: Lucas Stach <l.stach@pengutronix.de>; Deucher, Alexander <Alexand
> er.Deucher@amd.com>
> Cc: Grodzovsky, Andrey <Andrey.Grodzovsky@amd.com>; David Airlie <air
> lied@linux.ie>; amd-gfx@lists.freedesktop.org; patchwork-lst@pengutro
> nix.de; dri-devel@lists.freedesktop.org; kernel@pengutronix.de
> Subject: Re: [PATCH 0/2] Move scheduler out of AMDGPU
> 
> Am 01.12.2017 um 16:28 schrieb Lucas Stach:
> > Hi all,
> > 
> > so this is the first step to make the marvelous AMDGPU scheduler 
> > useable for other drivers. I have a (mostly) working prototype of 
> > Etnaviv using the scheduler, but those patches need to keep baking
> > for a while.
> > 
> > I'm sending this out as I want to avoid rebasing this change too
> > much 
> > and don't want to take people by surprise when the Etnaviv 
> > implementation surfaces. Also this might need some coordination 
> > between AMDGPU and Etnaviv, which might be good to get going now.
> > 
> > Please speak up now if you have any objections or comments.
> 
> Looks good to me, but question is what is this based upon?
> 
> I strongly assume drm-next, so question is now if we have any patches
> inside amd branches we should apply before doing this.
> 
> CCing Andrey as well cause he has some tasks assigned around the
> scheduler as well.
> 
> Regards,
> Christian.
> 
> > 
> > Regards,
> > Lucas
> > 
> > Lucas Stach (2):
> >    drm: move amd_gpu_scheduler into common location
> >    drm/sched: move fence slab handling to module init/exit
> > 
> >   drivers/gpu/drm/Kconfig                            |   5 +
> >   drivers/gpu/drm/Makefile                           |   1 +
> >   drivers/gpu/drm/amd/amdgpu/Makefile                |   5 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu.h                |  16 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c             |   8 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c            |  38 +--
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_device.c         |  12 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c            |   8 -
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c          |   4 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_job.c            |  22 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c           |  14 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_ring.h           |  12 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_sched.c          |  20 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_sched.h          |   2 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c           |   6 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c            |   8 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h            |   4 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c            |   8 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.h            |   4 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c            |   8 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_vce.h            |   2 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c            |  14 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.h            |   4 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c             |  10 +-
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h             |   4 +-
> >   drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c              |   4 +-
> >   drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c              |   8 +-
> >   drivers/gpu/drm/amd/amdgpu/uvd_v7_0.c              |   8 +-
> >   drivers/gpu/drm/amd/scheduler/gpu_scheduler.h      | 185 --------
> > ------
> >   drivers/gpu/drm/scheduler/Makefile                 |   4 +
> >   .../gpu/drm/{amd => }/scheduler/gpu_scheduler.c    | 281
> > +++++++++++----------
> >   drivers/gpu/drm/{amd => }/scheduler/sched_fence.c  | 122 +++++---
> > -
> >   include/drm/gpu_scheduler.h                        | 171
> > +++++++++++++
> >   .../drm/gpu_scheduler_trace.h                      |  14 +-
> >   34 files changed, 525 insertions(+), 511 deletions(-)
> >   delete mode 100644 drivers/gpu/drm/amd/scheduler/gpu_scheduler.h
> >   create mode 100644 drivers/gpu/drm/scheduler/Makefile
> >   rename drivers/gpu/drm/{amd => }/scheduler/gpu_scheduler.c (64%)
> >   rename drivers/gpu/drm/{amd => }/scheduler/sched_fence.c (58%)
> >   create mode 100644 include/drm/gpu_scheduler.h
> >   rename drivers/gpu/drm/amd/scheduler/gpu_sched_trace.h => 
> > include/drm/gpu_scheduler_trace.h (83%)
> > 
> 
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2017-12-04  9:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 15:28 [PATCH 0/2] Move scheduler out of AMDGPU Lucas Stach
2017-12-01 15:29 ` [PATCH 1/2] drm: move amd_gpu_scheduler into common location Lucas Stach
     [not found] ` <20171201152901.3626-1-l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-12-01 15:29   ` [PATCH 2/2] drm/sched: move fence slab handling to module init/exit Lucas Stach
2017-12-01 15:55   ` [PATCH 0/2] Move scheduler out of AMDGPU Christian König
2017-12-01 16:04     ` Lucas Stach
     [not found]     ` <7a884709-8717-cf45-152d-60bf8cb0f7e2-5C7GfCeVMHo@public.gmane.org>
2017-12-02 12:14       ` Liu, Monk
     [not found]         ` <BLUPR12MB04491E836AFBE4759784405E843E0-7LeqcoF/hwpTIQvHjXdJlwdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-12-04  9:42           ` Lucas Stach [this message]
2017-12-04 21:47       ` Alex Deucher
     [not found]         ` <CADnq5_OpH9eZ0iy5jRhY+_SNuUDi2yCL+XWHxa53t2UQVOcqGw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-05  9:18           ` Lucas Stach
2017-12-05 22:31             ` Alex Deucher

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=1512380573.6394.1.camel@pengutronix.de \
    --to=l.stach-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
    --cc=Andrey.Grodzovsky-5C7GfCeVMHo@public.gmane.org \
    --cc=Christian.Koenig-5C7GfCeVMHo@public.gmane.org \
    --cc=Monk.Liu-5C7GfCeVMHo@public.gmane.org \
    --cc=airlied-cv59FeDIM0c@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=patchwork-lst-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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