[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2025042227-crumb-rubble-7854@gregkh>
Date: Tue, 22 Apr 2025 14:17:48 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Jacek Lawrynowicz <jacek.lawrynowicz@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Karol Wachowski <karol.wachowski@...el.com>
Subject: Re: [PATCH] accel/ivpu: Add handling of
VPU_JSM_STATUS_MVNCI_CONTEXT_VIOLATION_HW
On Tue, Apr 08, 2025 at 11:57:11AM +0200, Jacek Lawrynowicz wrote:
> From: Karol Wachowski <karol.wachowski@...el.com>
>
> commit dad945c27a42dfadddff1049cf5ae417209a8996 upstream.
>
> Trigger recovery of the NPU upon receiving HW context violation from
> the firmware. The context violation error is a fatal error that prevents
> any subsequent jobs from being executed. Without this fix it is
> necessary to reload the driver to restore the NPU operational state.
>
> This is simplified version of upstream commit as the full implementation
> would require all engine reset/resume logic to be backported.
We REALLY do not like taking patches that are not upstream. Why not
backport all of the needed patches instead, how many would that be?
Taking one-off patches like this just makes it harder/impossible to
maintain the code over time as further fixes in this same area will NOT
apply properly at all.
Think about what you want to be touching 5 years from now, a one-off
change that doesn't match the rest of the kernel tree, or something that
is the same?
thanks,
greg k-h
Powered by blists - more mailing lists