linux-kernel - Re: [REGRESSION][BISECTED] vmwgfx crashes with command buffer error after update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e345252b-9370-4491-ac5d-d2dbe1005451@mailbox.org>
Date: Fri, 16 Aug 2024 22:23:54 +0200
From: Andreas Piesk <a.piesk@...lbox.org>
To: Zack Rusin <zack.rusin@...adcom.com>
Cc: bcm-kernel-feedback-list@...adcom.com, christian@...sel.eu,
 dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
 maaz.mombasawala@...adcom.com, martin.krastev@...adcom.com,
 rdkehn@...il.com, regressions@...ts.linux.dev, spender@...ecurity.net
Subject: Re: [REGRESSION][BISECTED] vmwgfx crashes with command buffer error
 after update

Am 16.08.24 um 20:56 schrieb Zack Rusin:
> 
> Thanks! I see. I have a patch out that fixes it, but in general I
> think those vm's with 16mb for graphics are very risky and I'd suggest
> bumping them to at least 32mb. The vram portion can stay at 16mb, but
> the graphicsMemoryKB can be safely set to fourth or even half of
> memsize (in your config 256mb or even 512mb), which will make the vm's
> a lot safer and allow actual ui usage because with console being
> pinned we just don't have a lot of wiggle room otherwise and we just
> can't migrate pinned framebuffers.
> The patch that "regressed" this makes dumb buffers surface that
> actually respect pinning, but as long as you don't have gpu host side
> things will be ok. Otherwise we can't make a config with 16mb of
> available graphics memory and graphics acceleration work.

Thanks for the looking into it and fixing it.
The explanation with details is much appreciated and I will keep your suggestions in mind.
I just used the VMware defaults for Linux 6.x+ in ESXi 8, maybe they should be bumped up a little bit.

Best,
-ap