Re: About migrating framebuffers in multi-GPU compositors

2022-03-24 Thread Alex Deucher
On Thu, Mar 24, 2022 at 3:40 PM Hoosier, Matt wrote: > > On Thu, 2022-03-24 at 15:28 -0400, Alex Deucher wrote: > > CAUTION - EXTERNAL EMAIL: Do not click any links or open any attachments > unless you trust the sender and know the content is safe. > > > > On Thu, Mar 24, 2022 at 9:43 AM Hoosier,

Re: About migrating framebuffers in multi-GPU compositors

2022-03-24 Thread Hoosier, Matt
On Thu, 2022-03-24 at 15:28 -0400, Alex Deucher wrote: CAUTION - EXTERNAL EMAIL: Do not click any links or open any attachments unless you trust the sender and know the content is safe. On Thu, Mar 24, 2022 at 9:43 AM Hoosier, Matt < matt.hoos...@garmin.com

Re: About migrating framebuffers in multi-GPU compositors

2022-03-24 Thread Alex Deucher
On Thu, Mar 24, 2022 at 9:43 AM Hoosier, Matt wrote: > > On Thu, 2022-03-24 at 11:56 +0200, Pekka Paalanen wrote: > > On Wed, 23 Mar 2022 14:19:08 + > > "Hoosier, Matt" < > > matt.hoos...@garmin.com > > > wrote: > > > Hi, > > > I recently had a reason to wade through Mutter's code to support >

Re: About migrating framebuffers in multi-GPU compositors

2022-03-24 Thread Pekka Paalanen
On Thu, 24 Mar 2022 13:43:02 + "Hoosier, Matt" wrote: > On Thu, 2022-03-24 at 11:56 +0200, Pekka Paalanen wrote: ... > This MR cover letter has a better overview of all the methods: > > > > https://gitlab.gnome.org/GNOME/mutter/

Re: About migrating framebuffers in multi-GPU compositors

2022-03-24 Thread Hoosier, Matt
On Thu, 2022-03-24 at 11:56 +0200, Pekka Paalanen wrote: On Wed, 23 Mar 2022 14:19:08 + "Hoosier, Matt" < matt.hoos...@garmin.com > wrote: Hi, I recently had a reason to wade through Mutter's code to support systems with more than one GPU. I was a bit

Re: About migrating framebuffers in multi-GPU compositors

2022-03-24 Thread Pekka Paalanen
On Wed, 23 Mar 2022 14:19:08 + "Hoosier, Matt" wrote: > Hi, > > I recently had a reason to wade through Mutter's code to support > systems with more than one GPU. I was a bit surprised to see that > it supports several different strategies for dealing with > scanning out a buffer on a KMS ou