Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp6818533rwn; Tue, 13 Sep 2022 09:22:41 -0700 (PDT) X-Google-Smtp-Source: AMsMyM54xBx5NkHcDEJg4amPTMlM+gjYz2iJXbzoz8N4NJPfvZVzowZN3/lyxa4hTsh0Zlgww5R+ X-Received: by 2002:a17:90b:2743:b0:200:9be5:d492 with SMTP id qi3-20020a17090b274300b002009be5d492mr51991pjb.237.1663086160483; Tue, 13 Sep 2022 09:22:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663086160; cv=none; d=google.com; s=arc-20160816; b=1EcYz6zDa5L5Ne7gD/XVrbEV+l+/yokLpO4skgkxeACHaHFVRx1+Wo4Oz14CN/LLyO ujDB4RMPJbXjmH396tsQ7Ipm+4/P+KsKpT8u0PlUpCs/KBZ1N9JgpfXJy01akt40AYS9 MPCQ8KPt2VoRuhhJtpohNRsO+0xoT//biyOba9RhQJRF0dZ05p1pBmQt/AHM3ZVnbXMs hwlZ5qqcwESMPzBIkhO+WMUavLNFUUAbCHwWMjbupKjWhrtiM3jrv/KkPwaruGxMz795 uZ3SD+QZb86Y01OSufGio4s1/8VynTamRsjhi7Szlcn7usQpix5tNa90La7s4PmJx/Sy 1gMg== 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 :message-id:references:in-reply-to:user-agent:subject:cc:to:from :date:feedback-id:dkim-signature:dkim-signature; bh=vzmZrlkHVtjeQn3abrVkqwXk0KmGWfY5VV/JgXRRvwg=; b=rxzYdHP29XxlaYdExLJ/2QUlswRUCEnqSgFfxeXs5lyG97XEtle+Arg4RrE9r/pVb0 IV/axRv5cufVEkINK6ryOMykV1wygwbjLm32JsEua4Jplx2lhQ8ACr16Zi+94UBgcnaF H2ELU8JEkq+j5W/zuTdKS1sqwpG+78e7sEuLd/7hwjLJJrnZ2VKxCs7WC7LYCdId1yjE Eg37J9/XuJ212VNaO6clGTG4e8ULFPRKVKrKZ8QgqjHomkPEGe4/eCdrzi0xSvRpssab n77xE0Sid9/ZNakTNQp/+tXdIe59/R+C8ezx+SCDBlCP1l3eRwfI31456vcvSSYGkN8m /MpA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mendozajonas.com header.s=fm1 header.b=Pp56YvG5; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=OCUxH1Tr; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k9-20020aa788c9000000b005251a2f06bbsi12815059pff.59.2022.09.13.09.22.28; Tue, 13 Sep 2022 09:22:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@mendozajonas.com header.s=fm1 header.b=Pp56YvG5; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=OCUxH1Tr; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232307AbiIMNgK (ORCPT + 99 others); Tue, 13 Sep 2022 09:36:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43016 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232305AbiIMNgI (ORCPT ); Tue, 13 Sep 2022 09:36:08 -0400 Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DBA335756D; Tue, 13 Sep 2022 06:36:03 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 642A73200970; Tue, 13 Sep 2022 09:36:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 13 Sep 2022 09:36:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= mendozajonas.com; h=cc:cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to; s=fm1; t=1663076161; x=1663162561; bh=vzmZrlkHVtjeQn3abrVkqwXk0 KmGWfY5VV/JgXRRvwg=; b=Pp56YvG51SfqJDwsGEBeqMqh1abGYWmLEX2DlX9KO 3aNocjuVTHKXfgPYTR9kyCvN4WW1tPYR7ZaKryizlpLFaKCeo6f6yKYDWTmabo9C 3U6yBibyQr7/HjvfzIJIFzQwLsETd/bOkPoJt8zBuD9AnRK59/NV5KIc6G+m7vzJ HKEH35Sr8/+CNjm2U0JIQNqDJv4TdFh5hNnDqOQ4fQiJVhT1IHtiBcU5c7O1B2UX 0u2y3eZ/turgo0nJTxuYMsXrcT0bRl14uO0uXLKYSNlSGkDm6cxp89BaLVOFLB46 0judMWj4QYSUJjcpZm65w+hTvG6JQG3WXOF48CKjEK9cg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1663076161; x= 1663162561; bh=vzmZrlkHVtjeQn3abrVkqwXk0KmGWfY5VV/JgXRRvwg=; b=O CUxH1Trj83doNkxwJqvUzsBeOGw+E8+s/lhgrkD5abMEAJxZ0Z4CJFUadGwc6fVd xysmN2vXL9lbQ3eBU82GzteGrL6TtZzLyM0aLA+pWk5osYP/EaK4B2NgJHEMtzx7 xrr/dxmgRZyI/b4EVNt7zlXSRZwae+ojsQ3/TpoZ0vclWS2kmVweQVu5MKVWuwki 9UZkorDk+cE4YWIglbpLX2JA363e3bzNh3jkzhQyjMNkU/9gA2WyzCzwdVYl6R5W vopIK3mrGn4RRPVn1b/PssMykV2tDSxyG81yylQ2SNrZBbyrvC/FgoBxNj0aFpor bbNjXvUwVJDxtVBjsbzUQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfedugedgieekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevufgfjghfkfggtgfgsehtqhhmtddtreejnecuhfhrohhmpefurghm ucfovghnughoiigrqdflohhnrghsuceoshgrmhesmhgvnhguohiirghjohhnrghsrdgtoh hmqeenucggtffrrghtthgvrhhnpeehudevffeuieefffehteekfeekledvhfehteejgeeg gedthfdvkeetleevhfelkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehsrghmsehmvghnughoiigrjhhonhgrshdrtghomh X-ME-Proxy: Feedback-ID: iab794258:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 13 Sep 2022 09:36:01 -0400 (EDT) Date: Tue, 13 Sep 2022 14:35:59 +0100 From: Sam Mendoza-Jonas To: Jiaqing Zhao , Paul Fertser CC: "David S. Miller" , Eric Dumazet , Paolo Abeni , netdev@vger.kernel.org, openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] net/ncsi: Add Intel OS2BMC OEM command User-Agent: K-9 Mail for Android In-Reply-To: <36c12486-57d4-c11d-474f-f26a7de8e59a@linux.intel.com> References: <20220909025716.2610386-1-jiaqing.zhao@linux.intel.com> <8eabb29b-7302-d0a2-5949-d7aa6bc59809@linux.intel.com> <36c12486-57d4-c11d-474f-f26a7de8e59a@linux.intel.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On September 13, 2022 3:12:06 AM GMT+01:00, Jiaqing Zhao wrote: > > >On 2022-09-09 15:43, Paul Fertser wrote: >> Hello, >>=20 >> On Fri, Sep 09, 2022 at 03:34:53PM +0800, Jiaqing Zhao wrote: >>>> Can you please outline some particular use cases for this feature? >>>> >>> It enables access between host and BMC when BMC shares the network con= nection >>> with host using NCSI, like accessing BMC via HTTP or SSH from host=2E= =20 >>=20 >> Why having a compile time kernel option here more appropriate than >> just running something like "/usr/bin/ncsi-netlink --package 0 >> --channel 0 --index 3 --oem-payload 00000157200001" (this example uses >> another OEM command) on BMC userspace startup? >>=20 > >Using ncsi-netlink is one way, but the package and channel id is undeterm= ined >as it is selected at runtime=2E Calling the netlink command on a nonexist= ent >package/channel may lead to kernel panic=2E If so, that would be a bug :) > >Why I prefer the kernel option is that it applies the config to all ncsi >devices by default when setting up them=2E This reduces the effort and ke= eps >compatibility=2E Lots of things in current ncsi kernel driver can be done= via >commands from userspace, but I think it is not a good idea to have a driv= er >resides on both kernel and userspace=2E BMCs are of course in their own world and there's already some examples of= the config option, but how would a system owner be able to disable this wi= thout reflashing the BMC?