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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EBC5AC4167B for ; Fri, 8 Dec 2023 05:29:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233028AbjLHF33 (ORCPT ); Fri, 8 Dec 2023 00:29:29 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56002 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229476AbjLHF31 (ORCPT ); Fri, 8 Dec 2023 00:29:27 -0500 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9417E1716 for ; Thu, 7 Dec 2023 21:29:32 -0800 (PST) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9BFB1C433C8; Fri, 8 Dec 2023 05:29:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1702013372; bh=UsILT93r2k6n3TCqbrECLHZ5VzzDB9sDuQ3fq/CaaLg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uQ4nidSrLr3sx5zj4XZhOy/B9Pg9OjuoSqb2SQ3q4Wo7ScYmCdVeIKa4cXOXZvZ0Z yNis7aVc2K7fVoihnX04GXN7iiFPkpNb5jsgHecW1vrBa/DQfuBaYDTYD/cWB3fVj+ 1OpltY3UkFEtus7g52w0YdYMd3s3SdbxqkVb1nWY= Date: Fri, 8 Dec 2023 06:29:29 +0100 From: Greg Kroah-Hartman To: Saeed Mahameed Cc: Aron Silverton , Jakub Kicinski , Jason Gunthorpe , David Ahern , Arnd Bergmann , Leon Romanovsky , Jiri Pirko , Leonid Bloch , Itay Avraham , linux-kernel@vger.kernel.org, Saeed Mahameed Subject: Re: [PATCH V3 2/5] misc: mlx5ctl: Add mlx5ctl misc driver Message-ID: <2023120832-vegan-trustable-f89a@gregkh> References: <2023112922-lyricist-unclip-8e78@gregkh> <20231204185210.030a72ca@kernel.org> <20231205204855.52fa5cc1@kernel.org> <20231207092329.3ec04dca@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 07, 2023 at 11:02:36AM -0800, Saeed Mahameed wrote: > I would like to add that debugfs is usually used to expose the driver > software states, as it evolves and changes with the driver code, but as I > explained in the other email, it's clearly not a good solution to expose > arbitrary objects of complex devices, that require interactive and > selective debug interfaces tailored to the user use-case. Why not? Remember, the only rule in debugfs is "there are no rules!" Well, there is one practical one, "do not rely on debugfs for any functioning system properties", i.e. "if access to debugfs is not present, or something in debugfs breaks, the kernel should continue to work just fine with no change in operations". But that's an overall system-level rule, not a rule for what you can put into debugfs. Have fun! greg k-h