Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp1487415ybh; Fri, 13 Mar 2020 02:04:24 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvFeBDSvoA6neta/5suURJYxvFh1PU6QlSI8OI4oWTbSi4QUbtrxNzDn+xKk8yfI1KMhlhF X-Received: by 2002:a05:6830:1b6f:: with SMTP id d15mr3698840ote.285.1584090264163; Fri, 13 Mar 2020 02:04:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584090264; cv=none; d=google.com; s=arc-20160816; b=O+bEEZtPl0jBrC54v/W+qQBXXo3ZP51SjX53XSCLrtw9nEFPSdRbRAXcNLVufFcMLi 2TPIhXhsA/qsw7lUajWFfSWSR6yBYINus8/txuV+6jp3+sH43W78SS1MOMi6BSYVJXU+ yjAujTzU6qPurO6QU9zUc9DrAXpw66MVOeajBL/5gqHm6jg3Zznt2iej8tFBWTdODoa4 CzsBw86ZXbWx8ZNXSYY8e1SKqjY3E/rFfGpKaEDdmQxuMAicQha0Uj+8HT9BxPvpcdIn h6sjrw8LnyrnqKnnujhIfko6vjHeLL9h+tdl70YyN4pV8PSA6Q9bo+IpmxVNEPGgPdsI sFog== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=Vvne4NmQMsx6g4loM7QHBP667L/jofmvChSXOamwPxM=; b=sA8bEBD5Cy+5PKpMkQ/uhKShP50APCCH3f1O8B7wsUVfQA3qo73MRnAcNUACduS/gX TipmppM11zeytlGzkVFIs2pZMVYpoZAw1r//r+FdTLpFEHWuAoKW9ZP/0F34gZixOh+d p4b6xFVUVOxevVpherhsIwOoI/N47nhjj+k871KG9kH0OPIEAKnVe+ZRxN2ThJqhBolD fafVtFAmkoF2gAyOZ0Drr4ulaoacOLJOwhT5DtU2Y9gyRQ/sTAL3FO3TDFUwZW2DE5ip EfvV1S7bnGdrmvHcSU6IMMaYMZ2lFnIxssXeaRdmX79gjcH/BSYWJvrVEqRsf0tJHsm6 zZ3A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e2si3958607otr.30.2020.03.13.02.04.11; Fri, 13 Mar 2020 02:04:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726426AbgCMJDo (ORCPT + 99 others); Fri, 13 Mar 2020 05:03:44 -0400 Received: from asavdk4.altibox.net ([109.247.116.15]:38446 "EHLO asavdk4.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726310AbgCMJDo (ORCPT ); Fri, 13 Mar 2020 05:03:44 -0400 Received: from ravnborg.org (unknown [158.248.194.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by asavdk4.altibox.net (Postfix) with ESMTPS id A633C804D0; Fri, 13 Mar 2020 10:03:39 +0100 (CET) Date: Fri, 13 Mar 2020 10:03:38 +0100 From: Sam Ravnborg To: Gerd Hoffmann Cc: dri-devel@lists.freedesktop.org, marmarek@invisiblethingslab.com, David Airlie , open list , "open list:DRM DRIVER FOR BOCHS VIRTUAL GPU" Subject: Re: [PATCH v3] drm/bochs: downgrade pci_request_region failure from error to warning Message-ID: <20200313090338.GA31815@ravnborg.org> References: <20200313084152.2734-1-kraxel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200313084152.2734-1-kraxel@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=XpTUx2N9 c=1 sm=1 tr=0 a=UWs3HLbX/2nnQ3s7vZ42gw==:117 a=UWs3HLbX/2nnQ3s7vZ42gw==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=8nJEP1OIZ-IA:10 a=vkfgAjWNAAAA:8 a=20KFwNOVAAAA:8 a=7gkXJVJtAAAA:8 a=XvIV5Jx4ir0DwZFBozwA:9 a=wPNLvfGTeEIA:10 a=s88AYcEWOXMFsoP9cgP2:22 a=E9Po1WZjFZOl8hwRPBS3:22 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Gred. On Fri, Mar 13, 2020 at 09:41:52AM +0100, Gerd Hoffmann wrote: > Shutdown of firmware framebuffer has a bunch of problems. Because > of this the framebuffer region might still be reserved even after > drm_fb_helper_remove_conflicting_pci_framebuffers() returned. > > Don't consider pci_request_region() failure for the framebuffer > region as fatal error to workaround this issue. > > Reported-by: Marek Marczykowski-G?recki > Signed-off-by: Gerd Hoffmann > --- > drivers/gpu/drm/bochs/bochs_hw.c | 6 ++---- > 1 file changed, 2 insertions(+), 4 deletions(-) > > diff --git a/drivers/gpu/drm/bochs/bochs_hw.c b/drivers/gpu/drm/bochs/bochs_hw.c > index 952199cc0462..dce4672e3fc8 100644 > --- a/drivers/gpu/drm/bochs/bochs_hw.c > +++ b/drivers/gpu/drm/bochs/bochs_hw.c > @@ -157,10 +157,8 @@ int bochs_hw_init(struct drm_device *dev) There is a drm_device avilable. > size = min(size, mem); > } > > - if (pci_request_region(pdev, 0, "bochs-drm") != 0) { > - DRM_ERROR("Cannot request framebuffer\n"); > - return -EBUSY; > - } > + if (pci_request_region(pdev, 0, "bochs-drm") != 0) > + DRM_WARN("Cannot request framebuffer, boot fb still active?\n"); So you could use drm_WARN() which is what is preferred these days. With this fixed: Acked-by: Sam Ravnborg Sam