Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1974818pxb; Fri, 5 Mar 2021 04:33:06 -0800 (PST) X-Google-Smtp-Source: ABdhPJySPi3OCzavq4eauqyHJH+My9XAGEvOoqLqyTFu6ifIssOKV85mA+iL0hyiiZAzn2QA3O22 X-Received: by 2002:aa7:c9cf:: with SMTP id i15mr8835725edt.296.1614947585868; Fri, 05 Mar 2021 04:33:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614947585; cv=none; d=google.com; s=arc-20160816; b=sTHMLrWi9g/OKu1EHI+ovcaLnb4xLTRdQ/otokhyMaAEbnjCqF7jfMBIrFvbtNNTiW 5TDaRoEqSEPSlu9aKDNmmGPBBgRmrM3pzaI6iXxF8DnvocX0Rb3zyZoCBBJCpSOii+cb U6tZDDUzVZH2ED+kfKfOsuYsPUidUzcPGjbGjiSnEHF61j1kiSy0UmTEj49DAof8JULg 1KOjl/HzYab5GVe3+nb9ZY1z1+axbx3dvggOR/TvXBBKYIYTMVRTGH2s86vPHz+IZqQU BLLdBhAwhztu8t+8Y6qzpfpE9Fo4X3pcjDvShcaNyAvXWN4Vjm63XSko5hmtpbmt6Ajz PgPg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=44XuMAqcEcG7RCc8gk5uF9FAC2j/sbAVuA1gJL73Qb8=; b=D2GcCKMRcpwYDVsDpltWsorzukhYGBTEM4+OpvLoLnkUhdWmPHgPcmUDXwa6ZaXIZr GZ/fN8hWYv7C6YbycLL7gF471NZouGcvMTAe2yF1EQ4CVgu5hFGIUdVUYduXnNUmDe59 uQaocjs0p/p2rQZj5//X0CE00E5tXFivKw0GhEIlocAPn/1aXXEmbRE/8C1/HfoXQ6eO BU6V1osZPAYfS14lUpg3L/FdRPhlvteaKpBaE37CIdIzHkr6jeuDj1GipPQu9Br1KDC1 cSvqGjdacG3bz42l8ySz/w/N5LPsFK/fV87K7L1f+R8Y88BokXbrqw48xalIDRiZ1j+C c5hg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=uJbf4OCV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i15si1499665edl.581.2021.03.05.04.32.43; Fri, 05 Mar 2021 04:33:05 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=uJbf4OCV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231206AbhCEMb0 (ORCPT + 99 others); Fri, 5 Mar 2021 07:31:26 -0500 Received: from mail.kernel.org ([198.145.29.99]:40326 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230516AbhCEMah (ORCPT ); Fri, 5 Mar 2021 07:30:37 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 5DC776501A; Fri, 5 Mar 2021 12:30:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1614947437; bh=+gNYgdiPN5ljdiYDoNP+TEofI6lHz2nhy+TQychr16w=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=uJbf4OCVbiGs2argigRjZ3GzWtT837mRJ2fV2Oq/9pB9j7R+YrtORqiFbQxMJHOFc lEenFhIGTCHxq7jovdiTMCLJFWOQHTVKjBtwzm/ZcDYqqhXtSxa0ia2GUEyoAuO2fC smFmFY/h8T3lerR6QsC0vRjdwkXZB8JWjJTQJDpY= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Jingwen Chen , Monk Liu , Alex Deucher , Sasha Levin Subject: [PATCH 5.10 064/102] drm/amd/amdgpu: add error handling to amdgpu_virt_read_pf2vf_data Date: Fri, 5 Mar 2021 13:21:23 +0100 Message-Id: <20210305120906.430202495@linuxfoundation.org> X-Mailer: git-send-email 2.30.1 In-Reply-To: <20210305120903.276489876@linuxfoundation.org> References: <20210305120903.276489876@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jingwen Chen [ Upstream commit 64dcf2f01d59cf9fad19b1a387bd39736a8f4d69 ] [Why] when vram lost happened in guest, try to write vram can lead to kernel stuck. [How] When the readback data is invalid, don't do write work, directly reschedule a new work. Signed-off-by: Jingwen Chen Reviewed-by: Monk Liu Signed-off-by: Alex Deucher Signed-off-by: Sasha Levin --- drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c index d0aea5e39531..e7678ba8fdcf 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c @@ -558,10 +558,14 @@ static int amdgpu_virt_write_vf2pf_data(struct amdgpu_device *adev) void amdgpu_virt_update_vf2pf_work_item(struct work_struct *work) { struct amdgpu_device *adev = container_of(work, struct amdgpu_device, virt.vf2pf_work.work); + int ret; - amdgpu_virt_read_pf2vf_data(adev); + ret = amdgpu_virt_read_pf2vf_data(adev); + if (ret) + goto out; amdgpu_virt_write_vf2pf_data(adev); +out: schedule_delayed_work(&(adev->virt.vf2pf_work), adev->virt.vf2pf_update_interval_ms); } -- 2.30.1