From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mout-p-103.mailbox.org (mout-p-103.mailbox.org [80.241.56.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8C74C1BD006 for ; Fri, 16 Aug 2024 20:24:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=80.241.56.161 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1723839851; cv=none; b=QF65VIPy4uxO2fTgozzBviJKUkxCMOGwOSxlG1DmCFmZYiJfgy8uYWJCNVsxy5Y73lD9HhD7nXQg5axyg7gl1D56VDcdTFn8Sc5AcYG8+n2IMiTdxmb1bK4M8MWlVnodDEhcSfqUjtT99LphH6STMIx+4KcGyMijzeMUfFNlhSA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1723839851; c=relaxed/simple; bh=WIYuYFHWdCQrD1vc4jBbvWdC6Mea0hURnFAGiSCYhC0=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=VyUGX8TgyO6xRKcYMSNw2eWVlGI1YHmeZJ1GQjELDYRvyTKHaINUNHWeOJpxBEGtlLfPvZRi2tWhfS8P+xhB6FQuOo/lyeNPt9ZtnWs1C9YrwQJQWtRYTEwhdtJ28NwF3bF2uawR3AYDq1BrukiSUoKXDy+NVysoxoSq3PYHdcw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=mailbox.org; spf=pass smtp.mailfrom=mailbox.org; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b=E0bkcHva; arc=none smtp.client-ip=80.241.56.161 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=mailbox.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=mailbox.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b="E0bkcHva" Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-103.mailbox.org (Postfix) with ESMTPS id 4Wltk76Mlqz9smd; Fri, 16 Aug 2024 22:23:59 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1723839839; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=y2a5uwxoWmK4hGq387/Bj9tHFW7u7XNQSFK7pAHa9AI=; b=E0bkcHvajiOa+ioQ9d6R959bOkg5yCiLLrj9cjdg22FWipTMe/cDKtzPFs0GeP26UVcMgX ziqA8k/nCKxqCXVYu+rc39h9GqoEmH9UOWiL4bL8Oo0TcWCHyafPo1RdhHlGRiTNZwQlSr SFAkQqhX24A8N1xSK6VhLU4h6RQQjSPjfQTPYdB6PUxPnczeMTTFNN3HVHJy6y8pgGUjH1 mppCFhVBQ2AX6Fes1RKvRKiHE04DD6YiQ7mdZ8DqeAuBQg0EAtIpW5hp1X2qTOalhv/Rhf Tpf67i9nUlR7y9LUS19Y0HhIxQKtpbkCZ9c4s0T7BqFTCxEvLZjE3mLbW9X0wg== Message-ID: Date: Fri, 16 Aug 2024 22:23:54 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [REGRESSION][BISECTED] vmwgfx crashes with command buffer error after update To: Zack Rusin Cc: bcm-kernel-feedback-list@broadcom.com, christian@heusel.eu, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, maaz.mombasawala@broadcom.com, martin.krastev@broadcom.com, rdkehn@gmail.com, regressions@lists.linux.dev, spender@grsecurity.net References: <40cf01ab-73ad-4243-b851-a02c377bdbde@mailbox.org> Content-Language: en-US From: Andreas Piesk In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-MBO-RS-META: jjckur8ysfr994hsbwpexesbwirt7yay X-MBO-RS-ID: 970057b013337eca572 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