[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bd8a3db62ccf91d980fb2124d6002868b6224423.camel@nvidia.com>
Date: Mon, 11 Dec 2023 14:10:09 +0000
From: Timur Tabi <ttabi@...dia.com>
To: "sashal@...nel.org" <sashal@...nel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
"daniel@...ll.ch" <daniel@...ll.ch>,
"bskeggs@...hat.com" <bskeggs@...hat.com>,
"airlied@...hat.com" <airlied@...hat.com>
Subject: Re: [PATCH AUTOSEL 6.1 13/29] nouveau/tu102: flush all pdbs on vmm
flush
On Mon, 2023-12-11 at 08:53 -0500, Sasha Levin wrote:
> This is a hack around a bug exposed with the GSP code, I'm not sure
> what is happening exactly, but it appears some of our flushes don't
> result in proper tlb invalidation for out BAR2 and we get a BAR2
> fault from GSP and it all dies.
Do we still want this hack on older kernels that don't support GSP?
Powered by blists - more mailing lists