From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 268D8C00528 for ; Wed, 5 Jul 2023 15:52:36 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id DBEDE10E17A; Wed, 5 Jul 2023 15:52:35 +0000 (UTC) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by gabe.freedesktop.org (Postfix) with ESMTPS id 537E410E17A for ; Wed, 5 Jul 2023 15:52:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1688572353; x=1720108353; h=date:message-id:from:to:cc:subject:in-reply-to: references:mime-version; bh=RVbEa/k4XGQYB6YG2jzwe3VwaIyCXIG1Fppx0BzqJzw=; b=HFw7JtdyclNO2A0ghukhafYwWvGKcSImKhEecF533VLpc1g8M7qK/Y7o ddew45DNbJZc2pBXRzNmDiNV2WyJ1FjSri4R0m3mSzk9BYlWjDMBR5rTY uvRGRfg/v3fSshAkhVUEDBXdykS4Fjjl/JLLitjdQj7p0ZPGHNu4B6cB+ HtyYtUmxOVm1v2W4V49Hbqj4oZDpF3TrM1iakffweHskf9IHM/37qTxRL z0tqiQqDjE9CEjgHUS2kvK3S2ILyiHiJymvtAs6WIzt4OqnFseaejBdNK Ek7IUp4os99r1zmOc8Fg+awYtrt3YY5bVIs6VaOBhcs+KBMsFDtNxi/IX w==; X-IronPort-AV: E=McAfee;i="6600,9927,10762"; a="449743103" X-IronPort-AV: E=Sophos;i="6.01,183,1684825200"; d="scan'208";a="449743103" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jul 2023 08:52:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10762"; a="754405888" X-IronPort-AV: E=Sophos;i="6.01,183,1684825200"; d="scan'208";a="754405888" Received: from adixit-mobl.amr.corp.intel.com (HELO adixit-arch.intel.com) ([10.209.1.248]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jul 2023 08:52:31 -0700 Date: Wed, 05 Jul 2023 08:47:17 -0700 Message-ID: <87wmzecqd6.wl-ashutosh.dixit@intel.com> From: "Dixit, Ashutosh" To: Nirmoy Das In-Reply-To: References: <20230705084403.3922130-1-tejas.upadhyay@intel.com> <87y1jucv1g.wl-ashutosh.dixit@intel.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/28.2 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Subject: Re: [Intel-xe] [PATCH V2] drm/xe: make GT sysfs init return void X-BeenThere: intel-xe@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel Xe graphics driver List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Andi Shyti , intel-xe@lists.freedesktop.org, Nirmoy Das Errors-To: intel-xe-bounces@lists.freedesktop.org Sender: "Intel-xe" On Wed, 05 Jul 2023 08:39:20 -0700, Nirmoy Das wrote: > > Hi Ashutosh, > > On 7/5/2023 4:06 PM, Dixit, Ashutosh wrote: > > On Wed, 05 Jul 2023 01:44:03 -0700, Tejas Upadhyay wrote: > >> Currently return from xe_gt_sysfs_init() is ignored > >> and also a failure in xe_gt_sysfs_init() isn't fatal > >> so make it return void. > > But why is the failure not fatal? I really don't understand the concept of > > these non-fatal failures. Do we really want to say the device is up if > > sysfs initialization has failed for some reason and people are unable to > > see card freq's e.g.? This was done in i915 but do we really want to repeat > > this for xe? IMO the simplest thing to do would be to fail the probe unless > > ALL required/intended functionality is clearly up. > > > I agree with the concern but the situation is different with a graphics > driver. > > If we return error on probe, (if I am not wrong) a user will have no way to > interact > > with the system other than ssh. We should ignore non-fatal error and let > the driver load > > so a user can have something to work with(may be report a bug :) ) Hmm, good point. Agreed :) This way though only display is critical and everything else non-critical? My point was knowing (or controlling) GPU freq's is a pretty important part of doing work on the GPU. In any case, since we are printing an error in dmesg if sysfs init fails, maybe converting to void is ok. So this is: Acked-by: Ashutosh Dixit > > > Regards, > > Nirmoy > > > > > Instead of ignoring the return, fail the probe? > > > > Thanks. > > -- > > Ashutosh