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 4FD3CCDB465 for ; Thu, 19 Oct 2023 15:24:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346146AbjJSPY4 (ORCPT ); Thu, 19 Oct 2023 11:24:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46040 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232938AbjJSPYy (ORCPT ); Thu, 19 Oct 2023 11:24:54 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 14B10124 for ; Thu, 19 Oct 2023 08:24:53 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 56A48C433C7; Thu, 19 Oct 2023 15:24:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1697729092; bh=Gs9uiuwgSdvAPbCatk5I/qMXRw9+2OVPvru9R4ouJIU=; h=Date:From:To:Cc:Subject:From; b=XjvlvFbQjLJAHl/2vyxmv8WzXMfPuS71UwTgUXGH10B9rFHjQmyBfsLJ6Wk+YGeJ6 4OYhMwqR3z2jw1eIzd9EGl0wm9SxXD8wzO4+OyIUPBBOoKKMoj6PEg6ERUbwHYnN1h F3F3Kn6eFERshJyAV6kpoD0Za4/pUOrfjvN+oxEU2UnojuVNHF/+JXjYBmNi0zxdHP EloHZ9lwD3XBESAKzdl3bLv66T1hPWpgyaEBoZY6iTDm1Yq7zG1M2xyZkFN7IWhSkJ 3/Vas9FCzVzWsliHqnD9WfEAC+Z2IbYAMJeFBnzXFMMhsS4oX05Uv39SHo0kdOeUC4 HF1zbRIsObANw== Date: Thu, 19 Oct 2023 08:24:51 -0700 From: Jakub Kicinski To: Saeed Mahameed Cc: Greg Kroah-Hartman , Leon Romanovsky , Jason Gunthorpe , Jiri Pirko , linux-kernel@vger.kernel.org, Arnd Bergmann Subject: Re: mlx5 ConnectX diagnostic misc driver Message-ID: <20231019082451.785aa123@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > The ConnectX HW family supported by the mlx5 drivers uses an architecture > where a FW component executes "mailbox RPCs" issued by the driver to make > changes to the device. This results in a complex debugging environment > where the FW component has information and complex low level state that > needs to be accessed to userspace for debugging purposes. You're being very dishonest towards Greg by not telling him that this is a networking device, and the networking maintainers explicitly nacked this backdoor. Nacked it, because you can't answer basic questions like "what are the use cases" with more than "custom config and debug". Whether Greg wants to take this into the "misc" pile is entirely up to him, but you gotta give him more context.