Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp1616919rwn; Fri, 9 Sep 2022 00:58:09 -0700 (PDT) X-Google-Smtp-Source: AA6agR7utmkyWtLqA7AM4Nj4EupGEOjgjFY1QShfzaYAuE1l/z2IsOh9c/CDQBkv4bRatSbvBNMS X-Received: by 2002:a17:903:2309:b0:176:de48:e940 with SMTP id d9-20020a170903230900b00176de48e940mr12673470plh.15.1662710289265; Fri, 09 Sep 2022 00:58:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662710289; cv=none; d=google.com; s=arc-20160816; b=H85eBDIaSgnoVNfqzEOf7KxtJ411i2fOKs8qUyU18/AyOYgsL3JX7p32jCKfZ856p4 yBQ2htRnRGSddS8BvHfFMHnT82vUUnza54tbLbQAadwZyrQB+SVBSQtjocsrD/Y8RRLJ n/UnORmBVY0RGhgNX8jyGB3ti+myPm5WLdozSi/0r27rYlPBGPeutv3On2DiVd1hiO// Mh4cQ4N7i4G2Slv4wrpb3uCZcW140Axsr87oI14hv6eK12JspJFK4kFHlCoNlDd/SNbS WcDmtZZNMI8pOFjf44Can7pWTgdiieqOt4k9GMoJ+0ocIH4KXtaADC8hmy6br57dxzBF gM9w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=oO8aR+OK3jm6MWHsvqg4tsEPqAjah2hP+M1tAWJdHBs=; b=lx5eJuIIJTyvPDJAkRVKooflIFk2LPapzG6kFDoa8HguNQ+C2wQQs2oxaxV/PqOLzr 7gvzEyOnn5u31plGumSsALINAEfj11lqFW3TT4SNpFmEcjWY9mz6mS1kP4PmCSmyho1K L0PnBBYkUnfURDdmFfetZqElcOvHFRpyjWLlTcD9KQ5QLWw4UDiRFk2I5OIrEtd2gxyY SxsjiEDh1wrlr0NF0/aC0LMCYV77mMyRg8NxHq+dc/05HVunSnNC8Y9zjUpZTrggBRuV 52AAFKIPt5xJunrvyNFF5tluG5MLDID1d6CjCEjbMRj2A4q5Js0ZW0rN8gIf7pO/0Ezb y83w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=ddkUvZ8g; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id i20-20020aa78d94000000b0052e4de9b806si1326931pfr.342.2022.09.09.00.57.57; Fri, 09 Sep 2022 00:58:09 -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=@intel.com header.s=Intel header.b=ddkUvZ8g; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231819AbiIIHju (ORCPT + 99 others); Fri, 9 Sep 2022 03:39:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38718 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231594AbiIIHiz (ORCPT ); Fri, 9 Sep 2022 03:38:55 -0400 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CE2ED4DF07; Fri, 9 Sep 2022 00:35:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1662708956; x=1694244956; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=m3YnqdItTBfQHuTJjhU/D3X2vYT7bLo7zCxA7BZS5Gg=; b=ddkUvZ8gAEZdc45JaMhFgdZxyPONLu341eDyd8/EiILhqJQd62dOhFcV mbrzL7j+oFmbBlfVetxwnimJe6zZwYoSzZUZQuUabp9AT3l54na7yU+MZ D7iXigyN0HR8Ok1KqF0bF4BBZVQkU2TThWnlBqIZHYhtdktwYEkYFD1eh HKuKYPWDyopWZRyAhMUUnVvbRSqxQUMfSEsSKKVujOYgMkPvXRR4wBVvd /RJMCMuPBPznOlSpcPpIsDSrblwndLGcuOfR8Cq8Kj+j920zN3fNSctZq FaP8FvRpgau/OjWODsH3v07ustfMzjkAuS8DsS4uF1WSnJaxsDCr8+oAB Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10464"; a="296155491" X-IronPort-AV: E=Sophos;i="5.93,302,1654585200"; d="scan'208";a="296155491" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Sep 2022 00:35:16 -0700 X-IronPort-AV: E=Sophos;i="5.93,302,1654585200"; d="scan'208";a="645435049" Received: from yuyongfe-mobl1.ccr.corp.intel.com (HELO [10.249.174.117]) ([10.249.174.117]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Sep 2022 00:35:11 -0700 Message-ID: <8eabb29b-7302-d0a2-5949-d7aa6bc59809@linux.intel.com> Date: Fri, 9 Sep 2022 15:34:53 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.1 Subject: Re: [PATCH] net/ncsi: Add Intel OS2BMC OEM command To: Paul Fertser Cc: Samuel Mendoza-Jonas , "David S. Miller" , Eric Dumazet , Paolo Abeni , netdev@vger.kernel.org, openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org References: <20220909025716.2610386-1-jiaqing.zhao@linux.intel.com> Content-Language: en-US From: Jiaqing Zhao In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE,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 2022-09-09 13:59, Paul Fertser wrote: > Hello, > > On Fri, Sep 09, 2022 at 10:57:17AM +0800, Jiaqing Zhao wrote: >> The Intel OS2BMC OEM NCSI command is used for controlling whether >> network traffic between host and sideband is allowed or not. By >> default such traffic is disallowed, meaning that if the device using >> NCS (usually BMC) does not have extra active connection, it cannot >> reach the host. > > Can you please explain the rationale behind introducing this as a > compile-time kernel config option? I can probably imagine how this can > make sense as a DT switch (e.g. to describe hardware where there's no > other communication channel between the host and BMC) but even this > feels far-fetched. Previously I submitted a patch to make the NCSI configurable in DT[1], but it was not accepted by kernel community. A limitation is that currently NCSI is not a standalone device node, it is controlled by "use-ncsi" option in the MAC device DT node (like ftgmac100). Other features like keep phy (also intel-specific oem) also uses kernel option. (CONFIG_NCSI_OEM_CMD_KEEP_PHY) [1] https://lore.kernel.org/netdev/20220610165940.2326777-4-jiaqing.zhao@linux.intel.com/T/ > Can you please outline some particular use cases for this feature? > It enables access between host and BMC when BMC shares the network connection with host using NCSI, like accessing BMC via HTTP or SSH from host.