From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bali.collaboradmins.com (bali.collaboradmins.com [148.251.105.195]) (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 1EDED29C325 for ; Mon, 16 Mar 2026 10:36:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=148.251.105.195 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773657406; cv=none; b=abLcDjY2Hh9NH6r4RfxnTN5+7QpvowQdP+0R8vGzbDWlrcnMBrhfsMRHKan+GDoU+PRKt566Hjt4Tgdz6I8PLWjfY6nzpeHmnIMruFpkZHeoZLRVjxOzXV93C+vU7Elqv6LFbVwMOZRslsnBPpSVDTGN2Ap+jFb7T0aPPxaZxWc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773657406; c=relaxed/simple; bh=eVt6F9ysICTFqDZVowFsKUa1CX+NqY9EvfoLuRRDj2g=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=JWnHBbwguGfwVxt1zxlOf0gR74V842eq59Q2XyaTIhYRGN3lrB+5LYH0ryjxvLnXZUyX37BF2HJS+VIY2r7+8tks6IJ0dDXmaaBgaCkqejuymfyzFUFw5qnkNIEGUwHPO9NURAA/bpBnNTK+Dj7XzzvebjIk+CTZL5igDb/Yh/8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=collabora.com; spf=pass smtp.mailfrom=collabora.com; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b=BzbaEhdP; arc=none smtp.client-ip=148.251.105.195 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=collabora.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=collabora.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b="BzbaEhdP" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1773657403; bh=eVt6F9ysICTFqDZVowFsKUa1CX+NqY9EvfoLuRRDj2g=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=BzbaEhdPFl1nercL2LPX/KBP7ChUMLmxhQCSj/VY6AaABaN/IwfYFwTbrpaILh8GX P12on44pBU1r2K9Lvb1cNLmGIyKRo0xQ8r3yMlGjbRVYTlt9jnVQsxfj61p9IZxrE5 OSkFQnAxBFJcVIkOU/Mwzj0PbSqo4o0Ik6aWznN3EgN5ZctmkRJ6oKLr0b+kqJHUQg JTlwu/CytfgN05ROQlwCKTOePzmiQaoTM1DgrlUibtc9e6MC7lCBG4aVOr6oMw3pr9 vTojriw0SjeLvafzKd+N+Omr/IzmzA3xGhZixRYicj33qcSjxry9XuT4y9nOJGs1IU tjk08IvmiO6ww== Received: from fedora (unknown [IPv6:2a01:e0a:2c:6930:d919:a6e:5ea1:8a9f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: bbrezillon) by bali.collaboradmins.com (Postfix) with ESMTPSA id 13B7F17E0E4C; Mon, 16 Mar 2026 11:36:43 +0100 (CET) Date: Mon, 16 Mar 2026 11:36:37 +0100 From: Boris Brezillon To: Thomas Zimmermann Cc: Pedro Demarchi Gomes , Maarten Lankhorst , Maxime Ripard , David Airlie , Simona Vetter , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3] drm/shmem-helper: Fix Map huge page mapping in fault handler Message-ID: <20260316113637.63a5031a@fedora> In-Reply-To: <08112162-7939-48b8-be57-790a8686bc46@suse.de> References: <20260316002649.211819-1-pedrodemargomes@gmail.com> <20260316105043.115ba8a3@fedora> <08112162-7939-48b8-be57-790a8686bc46@suse.de> Organization: Collabora X-Mailer: Claws Mail 4.3.1 (GTK 3.24.51; x86_64-redhat-linux-gnu) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 16 Mar 2026 11:14:40 +0100 Thomas Zimmermann wrote: > Am 16.03.26 um 10:50 schrieb Boris Brezillon: > > >> Avoid this race by adding a huge_fault callback to drm_gem_shmem_vm_ops so that > >> PMD-sized mappings are handled through the appropriate huge page fault path. > > This patch will conflict heavily with the folio-tracking patches that > has been merged into upstream DRM. How do we deal with that? We need a fix in drm-misc-fixes since it's a bug that exists in v7.0, and a conflict resolution recorded in drm-tip to deal with the drm-misc-fixes vs drm-misc-next conflicts (I don't remember the exact process, but it's documented in dim).