On Mon, Apr 03, 2023 at 05:22:01PM -0700, Matthew Brost wrote:
> Hello,
Hello,
Jumping a bit late on this thread as I was waiting on some approvals and then
holidays kicked in, but I would like to (re)introduce myself and the people
I work with and to let you know that we are interested in the
gt; > > > > handling ring flow control as Matt said)from drm scheduler, but push
> > > > > the
> > > > > dependency/completion tracking completely to user space using
> > > > > techniques such
> > > > > as user space fence. User space d
; faith.ekstr...@collabora.com
Subject: Re: [RFC PATCH 00/10] Xe DRM scheduler and long running workload
plans
On Wed, Apr 05, 2023 at 12:06:53PM -0600, Zeng, Oak wrote:
Hi,
Using dma-fence for completion/dependency tracking for long-run
workload(more precisely on-demand paging/page fault ena
On Sat, Apr 08, 2023 at 04:05:20PM +0900, Asahi Lina wrote:
> On 04/04/2023 10.58, Matthew Brost wrote:
> > On Tue, Apr 04, 2023 at 10:07:48AM +0900, Asahi Lina wrote:
> > > Hi, thanks for the Cc!
> > >
> >
> > No problem.
> >
> > > On 04/04/2023 09.22, Matthew Brost wrote:
> > > > Hello,
> > >
On Wed, Apr 12, 2023 at 02:47:52PM +0900, Asahi Lina wrote:
> On 11/04/2023 23.07, Daniel Vetter wrote:
> > On Sat, Apr 08, 2023 at 04:05:20PM +0900, Asahi Lina wrote:
> > > On 04/04/2023 10.58, Matthew Brost wrote:
> > > > On Tue, Apr 04, 2023 at 10:07:48AM +0900, Asahi Lina wrote:
> > > > > Hi,
On 11/04/2023 23.07, Daniel Vetter wrote:
On Sat, Apr 08, 2023 at 04:05:20PM +0900, Asahi Lina wrote:
On 04/04/2023 10.58, Matthew Brost wrote:
On Tue, Apr 04, 2023 at 10:07:48AM +0900, Asahi Lina wrote:
Hi, thanks for the Cc!
No problem.
On 04/04/2023 09.22, Matthew Brost wrote:
Hello,
> > > interact
> > > with fw scheduler. Use user fence for completion/dependency tracking.
> > > This is a hard no from me, I want 1 submission path in Xe. Either we use
> > > the DRM scheduler or we don't.
> > >
> > > Matt
> > >
>
On Sat, Apr 08, 2023 at 04:05:20PM +0900, Asahi Lina wrote:
> On 04/04/2023 10.58, Matthew Brost wrote:
> > On Tue, Apr 04, 2023 at 10:07:48AM +0900, Asahi Lina wrote:
> > > Hi, thanks for the Cc!
> > >
> >
> > No problem.
> >
> > > On 04/04/2023 09.22, Matthew Brost wrote:
> > > > Hello,
> > >
; thomas.hellst...@linux.intel.com;
airl...@linux.ie;
l...@asahilina.net; boris.brezil...@collabora.com;
faith.ekstr...@collabora.com
Subject: Re: [RFC PATCH 00/10] Xe DRM scheduler and long running workload
plans
Am 04.04.23 um 20:08 schrieb Matthew Brost:
On Tue, Apr 04, 2023 at 12:02:03PM -0600, Zeng
On 04/04/2023 10.58, Matthew Brost wrote:
On Tue, Apr 04, 2023 at 10:07:48AM +0900, Asahi Lina wrote:
Hi, thanks for the Cc!
No problem.
On 04/04/2023 09.22, Matthew Brost wrote:
Hello,
As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
have been asked to merge our
..@lists.freedesktop.org; robdcl...@chromium.org; airl...@linux.ie;
> l...@asahilina.net; boris.brezil...@collabora.com;
> faith.ekstr...@collabora.com
> Subject: Re: [RFC PATCH 00/10] Xe DRM scheduler and long running workload
> plans
>
> On Wed, Apr 05, 2023 at 12:06:53PM -0600,
On Thu, Apr 06, 2023 at 12:14:36PM +0200, Christian König wrote:
> Am 06.04.23 um 08:37 schrieb Daniel Vetter:
> > On Thu, Apr 06, 2023 at 02:08:10AM +, Matthew Brost wrote:
> > > On Wed, Apr 05, 2023 at 12:12:27PM +0200, Daniel Vetter wrote:
> > > > On Wed, 5 Apr 2023 at 11:57, Christian
Am 06.04.23 um 08:37 schrieb Daniel Vetter:
On Thu, Apr 06, 2023 at 02:08:10AM +, Matthew Brost wrote:
On Wed, Apr 05, 2023 at 12:12:27PM +0200, Daniel Vetter wrote:
On Wed, 5 Apr 2023 at 11:57, Christian König wrote:
Am 05.04.23 um 11:07 schrieb Daniel Vetter:
[SNIP]
I would approach
...@linux.intel.com; airl...@linux.ie;
l...@asahilina.net; boris.brezil...@collabora.com; faith.ekstr...@collabora.com
Subject: Re: [RFC PATCH 00/10] Xe DRM scheduler and long running workload
plans
Am 04.04.23 um 20:08 schrieb Matthew Brost:
On Tue, Apr 04, 2023 at 12:02:03PM -0600, Zeng, Oak wrote:
Hi
On Thu, Apr 06, 2023 at 02:08:10AM +, Matthew Brost wrote:
> On Wed, Apr 05, 2023 at 12:12:27PM +0200, Daniel Vetter wrote:
> > On Wed, 5 Apr 2023 at 11:57, Christian König
> > wrote:
> > >
> > > Am 05.04.23 um 11:07 schrieb Daniel Vetter:
> > > > [SNIP]
> > > >> I would approach it from the
On Wed, Apr 05, 2023 at 12:12:27PM +0200, Daniel Vetter wrote:
> On Wed, 5 Apr 2023 at 11:57, Christian König wrote:
> >
> > Am 05.04.23 um 11:07 schrieb Daniel Vetter:
> > > [SNIP]
> > >> I would approach it from the complete other side. This component here is
> > >> a
> > >> tool to decide
t; Sent: April 5, 2023 3:30 AM
> > To: Brost, Matthew ; Zeng, Oak
> >
> > Cc: dri-devel@lists.freedesktop.org; intel...@lists.freedesktop.org;
> > robdcl...@chromium.org; thomas.hellst...@linux.intel.com; airl...@linux.ie;
> > l...@asahilina.net; boris.brezil...@c
.brezil...@collabora.com;
> faith.ekstr...@collabora.com
> Subject: Re: [RFC PATCH 00/10] Xe DRM scheduler and long running workload
> plans
>
> Am 04.04.23 um 20:08 schrieb Matthew Brost:
> > On Tue, Apr 04, 2023 at 12:02:03PM -0600, Zeng, Oak wrote:
> >> Hi Matt
On Wed, 5 Apr 2023 at 11:57, Christian König wrote:
>
> Am 05.04.23 um 11:07 schrieb Daniel Vetter:
> > [SNIP]
> >> I would approach it from the complete other side. This component here is a
> >> tool to decide what job should run next.
> >>
> >> How that is then signaled and run should not be
Am 05.04.23 um 11:07 schrieb Daniel Vetter:
[SNIP]
I would approach it from the complete other side. This component here is a
tool to decide what job should run next.
How that is then signaled and run should not be part of the scheduler, but
another more higher level component.
This way you
On Wed, Apr 05, 2023 at 10:53:26AM +0200, Christian König wrote:
> Am 05.04.23 um 10:34 schrieb Daniel Vetter:
> > On Wed, Apr 05, 2023 at 09:41:23AM +0200, Christian König wrote:
> > > Am 04.04.23 um 15:37 schrieb Matthew Brost:
> > > > On Tue, Apr 04, 2023 at 11:13:28AM +0200, Christian König
Am 05.04.23 um 10:34 schrieb Daniel Vetter:
On Wed, Apr 05, 2023 at 09:41:23AM +0200, Christian König wrote:
Am 04.04.23 um 15:37 schrieb Matthew Brost:
On Tue, Apr 04, 2023 at 11:13:28AM +0200, Christian König wrote:
Hi,
Am 04.04.23 um 02:22 schrieb Matthew Brost:
Hello,
As a prerequisite
ian.
>
> >
> > Matt
> > > Thanks,
> > > Oak
> > >
> > > > -Original Message-
> > > > From: dri-devel On Behalf Of
> > > > Matthew Brost
> > > > Sent: April 3, 2023 8:22 PM
> > > > To: dr
On Wed, Apr 05, 2023 at 09:41:23AM +0200, Christian König wrote:
> Am 04.04.23 um 15:37 schrieb Matthew Brost:
> > On Tue, Apr 04, 2023 at 11:13:28AM +0200, Christian König wrote:
> > > Hi,
> > >
> > > Am 04.04.23 um 02:22 schrieb Matthew Brost:
> > > > Hello,
> > > >
> > > > As a prerequisite
Am 04.04.23 um 15:37 schrieb Matthew Brost:
On Tue, Apr 04, 2023 at 11:13:28AM +0200, Christian König wrote:
Hi,
Am 04.04.23 um 02:22 schrieb Matthew Brost:
Hello,
As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
have been asked to merge our common DRM scheduler patches
[RFC PATCH 00/10] Xe DRM scheduler and long running workload plans
Hello,
As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
have been asked to merge our common DRM scheduler patches first as well
as develop a common solution for long running workloads with the DRM
scheduler. This
On Tue, 4 Apr 2023 at 19:29, Tvrtko Ursulin
wrote:
>
>
> On 04/04/2023 14:52, Matthew Brost wrote:
> > On Tue, Apr 04, 2023 at 10:43:03AM +0100, Tvrtko Ursulin wrote:
> >>
> >> On 04/04/2023 01:22, Matthew Brost wrote:
> >>> Hello,
> >>>
> >>> As a prerequisite to merging the new Intel Xe DRM
..@linux.ie;
> > l...@asahilina.net; boris.brezil...@collabora.com; Brost, Matthew
> > ; christian.koe...@amd.com;
> > faith.ekstr...@collabora.com
> > Subject: [RFC PATCH 00/10] Xe DRM scheduler and long running workload plans
> >
> > Hello,
> >
> >
; faith.ekstr...@collabora.com
> Subject: [RFC PATCH 00/10] Xe DRM scheduler and long running workload plans
>
> Hello,
>
> As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
> have been asked to merge our common DRM scheduler patches first as well
> as d
On 04/04/2023 14:52, Matthew Brost wrote:
On Tue, Apr 04, 2023 at 10:43:03AM +0100, Tvrtko Ursulin wrote:
On 04/04/2023 01:22, Matthew Brost wrote:
Hello,
As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
have been asked to merge our common DRM scheduler patches first as
On Tue, Apr 04, 2023 at 10:43:03AM +0100, Tvrtko Ursulin wrote:
>
> On 04/04/2023 01:22, Matthew Brost wrote:
> > Hello,
> >
> > As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
> > have been asked to merge our common DRM scheduler patches first as well
> > as develop a
On Tue, Apr 04, 2023 at 11:48:36AM +0200, Christian König wrote:
> Am 04.04.23 um 11:43 schrieb Tvrtko Ursulin:
> >
> > On 04/04/2023 01:22, Matthew Brost wrote:
> > > Hello,
> > >
> > > As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
> > > have been asked to merge our
On Tue, Apr 04, 2023 at 11:13:28AM +0200, Christian König wrote:
> Hi,
>
> Am 04.04.23 um 02:22 schrieb Matthew Brost:
> > Hello,
> >
> > As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
> > have been asked to merge our common DRM scheduler patches first as well
> > as
On Tue, Apr 04, 2023 at 11:04:54AM +0200, Christian König wrote:
> Please make sure to CC Luben on scheduler patches.
>
Sure, figured I was missing a few people.
Matt
> Regards,
> Christian.
>
> Am 04.04.23 um 02:22 schrieb Matthew Brost:
> > Hello,
> >
> > As a prerequisite to merging the
Am 04.04.23 um 11:43 schrieb Tvrtko Ursulin:
On 04/04/2023 01:22, Matthew Brost wrote:
Hello,
As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
have been asked to merge our common DRM scheduler patches first as well
as develop a common solution for long running workloads
On 04/04/2023 01:22, Matthew Brost wrote:
Hello,
As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
have been asked to merge our common DRM scheduler patches first as well
as develop a common solution for long running workloads with the DRM
scheduler. This RFC series is our
Hi,
Am 04.04.23 um 02:22 schrieb Matthew Brost:
Hello,
As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
have been asked to merge our common DRM scheduler patches first as well
as develop a common solution for long running workloads with the DRM
scheduler. This RFC series is
Please make sure to CC Luben on scheduler patches.
Regards,
Christian.
Am 04.04.23 um 02:22 schrieb Matthew Brost:
Hello,
As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
have been asked to merge our common DRM scheduler patches first as well
as develop a common solution
On Tue, Apr 04, 2023 at 10:07:48AM +0900, Asahi Lina wrote:
> Hi, thanks for the Cc!
>
No problem.
> On 04/04/2023 09.22, Matthew Brost wrote:
> > Hello,
> >
> > As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
> > have been asked to merge our common DRM scheduler patches
Hi, thanks for the Cc!
On 04/04/2023 09.22, Matthew Brost wrote:
Hello,
As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
have been asked to merge our common DRM scheduler patches first as well
as develop a common solution for long running workloads with the DRM
scheduler.
Hello,
As a prerequisite to merging the new Intel Xe DRM driver [1] [2], we
have been asked to merge our common DRM scheduler patches first as well
as develop a common solution for long running workloads with the DRM
scheduler. This RFC series is our first attempt at doing this. We
welcome any
41 matches
Mail list logo
