Re: [PATCH] drm/vmwgfx: Filter modes which exceed 3/4 of graphics memory.

2024-02-06 Thread Daniel Stone
On Wed, 31 Jan 2024 at 02:31, Zack Rusin wrote: > On Tue, Jan 30, 2024 at 6:50 PM Daniel Stone wrote: > > The entire model we have is that basis timing flows backwards. The > > 'hardware' gives us a deadline, KMS angles to meet that with a small > > margin, the compositor angles to meet that

Re: [PATCH] drm/vmwgfx: Filter modes which exceed 3/4 of graphics memory.

2024-01-31 Thread Thomas Zimmermann
Hi Zack Am 30.01.24 um 20:38 schrieb Zack Rusin: On Fri, Jan 12, 2024 at 4:20 PM Ian Forbes wrote: SVGA requires surfaces to fit within graphics memory (max_mob_pages) which means that modes with a final buffer size that would exceed graphics memory must be pruned otherwise creation will

Re: [PATCH] drm/vmwgfx: Filter modes which exceed 3/4 of graphics memory.

2024-01-30 Thread Zack Rusin
On Tue, Jan 30, 2024 at 6:50 PM Daniel Stone wrote: > > Hi, > > On Tue, 30 Jan 2024 at 18:39, Zack Rusin wrote: > > In general, yes. Of course it's a little more convoluted because we'll > > act like OpenGL runtime here (i.e. glXSwapBuffers), i.e. our driver > > will fake page-flips because the

Re: [PATCH] drm/vmwgfx: Filter modes which exceed 3/4 of graphics memory.

2024-01-30 Thread Daniel Stone
Hi, On Tue, 30 Jan 2024 at 18:39, Zack Rusin wrote: > In general, yes. Of course it's a little more convoluted because we'll > act like OpenGL runtime here (i.e. glXSwapBuffers), i.e. our driver > will fake page-flips because the only memory we'll have is a single > buffer as the actual

Re: [PATCH] drm/vmwgfx: Filter modes which exceed 3/4 of graphics memory.

2024-01-30 Thread Zack Rusin
On Fri, Jan 12, 2024 at 4:20 PM Ian Forbes wrote: > > SVGA requires surfaces to fit within graphics memory (max_mob_pages) which > means that modes with a final buffer size that would exceed graphics memory > must be pruned otherwise creation will fail. > > Additionally, device commands which use

Re: [PATCH] drm/vmwgfx: Filter modes which exceed 3/4 of graphics memory.

2024-01-30 Thread Zack Rusin
On Fri, Jan 19, 2024 at 4:22 AM Thomas Zimmermann wrote: > > Hi > > Am 18.01.24 um 19:25 schrieb Zack Rusin: > > On Mon, Jan 15, 2024 at 3:21 AM Thomas Zimmermann > > wrote: > >> > >> Hi > >> > >> Am 12.01.24 um 21:38 schrieb Ian Forbes: > >>> SVGA requires surfaces to fit within graphics

Re: [PATCH] drm/vmwgfx: Filter modes which exceed 3/4 of graphics memory.

2024-01-19 Thread Thomas Zimmermann
Hi Am 18.01.24 um 19:25 schrieb Zack Rusin: On Mon, Jan 15, 2024 at 3:21 AM Thomas Zimmermann wrote: Hi Am 12.01.24 um 21:38 schrieb Ian Forbes: SVGA requires surfaces to fit within graphics memory (max_mob_pages) which means that modes with a final buffer size that would exceed graphics

Re: [PATCH] drm/vmwgfx: Filter modes which exceed 3/4 of graphics memory.

2024-01-18 Thread Zack Rusin
On Mon, Jan 15, 2024 at 3:21 AM Thomas Zimmermann wrote: > > Hi > > Am 12.01.24 um 21:38 schrieb Ian Forbes: > > SVGA requires surfaces to fit within graphics memory (max_mob_pages) which > > means that modes with a final buffer size that would exceed graphics memory > > must be pruned otherwise

Re: [PATCH] drm/vmwgfx: Filter modes which exceed 3/4 of graphics memory.

2024-01-15 Thread Thomas Zimmermann
Hi Am 12.01.24 um 21:38 schrieb Ian Forbes: SVGA requires surfaces to fit within graphics memory (max_mob_pages) which means that modes with a final buffer size that would exceed graphics memory must be pruned otherwise creation will fail. Additionally, device commands which use multiple

[PATCH] drm/vmwgfx: Filter modes which exceed 3/4 of graphics memory.

2024-01-12 Thread Ian Forbes
SVGA requires surfaces to fit within graphics memory (max_mob_pages) which means that modes with a final buffer size that would exceed graphics memory must be pruned otherwise creation will fail. Additionally, device commands which use multiple graphics resources must have all their resources fit