Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp130331ybl; Tue, 13 Aug 2019 17:23:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqxHceuUwg9Uosu+V8OyPp1dXIHJ1pyb29zA7KyiCwP573qqIp2wnnZhqCO9rwrNnUDSGwpA X-Received: by 2002:a63:1765:: with SMTP id 37mr37085959pgx.447.1565742221716; Tue, 13 Aug 2019 17:23:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565742221; cv=none; d=google.com; s=arc-20160816; b=Ku4mefZyVFZsmmP8pnLotIr4CTwen5hD/ONx83zBD56mvL/xUWhc41sgt5e2etHPJi FT09Hffr8Ovy8f+AQw4ju877/7OYeBaDcPlRt9mRuwq8Z+sVxZ5BqpdvEjZVw0ypKIDX LUISc7Va4e+JuT4jkRpFcbRwBQPwswBAahUoljVWMmx9l6sUQFG7QmC2otMz5kFXU1jx 4FmuK9Fzvs4j6yghoMY7hJq1qPeOP+HPW8ioPpigkNoslHEY6ILxI/dqMdaDzyPuLvHl zmp1BDGh+NL0V7xu5amTGoHt/p4b3rnLJ2Y5AfRxkZR+x6+8hTKAhvj1v0OYh0mk37+g o68Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:from:subject; bh=6oCSAXKfUCwCQ8DGCaGxfW+XA0OD/KKPV6lsBURGbYA=; b=S5R6aeNWe6T2bPTXXhBqfWhTJL4cMutaMIEsP8q0Q3JycnJB9lP5S3TTo+th1h9IzJ 6ZcYRUeRZr987cYInhWiyqo5vzU8esJnYqfb2CVMAiTTRVkM9AR2t+y0LErZFbJncv2p 4gTXfMU26e5/BNfUxFuXLvgKBf5YjadQWpgLj5AjWJCEihAW3mPCgp03gb0IIXHjJIhM qM+XSJTndzmfEhFL5+GMw8BbDq4cjEVwvnyyC47JeVF17e+VfTRKFh+FL4VW4HHBbNW0 dUyRLHUmQUpj35ExhlS057l9hZ1IQbc0OU7PYu1ieQhEvLJRHBiA/bSiNyGPe/rizLJt IrVQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m7si65287145pls.110.2019.08.13.17.23.23; Tue, 13 Aug 2019 17:23:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726597AbfHNAWV (ORCPT + 99 others); Tue, 13 Aug 2019 20:22:21 -0400 Received: from mga04.intel.com ([192.55.52.120]:13153 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726007AbfHNAWV (ORCPT ); Tue, 13 Aug 2019 20:22:21 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Aug 2019 17:22:21 -0700 X-IronPort-AV: E=Sophos;i="5.64,382,1559545200"; d="scan'208";a="167220997" Received: from tsduncan-ubuntu.jf.intel.com (HELO [10.7.169.130]) ([10.7.169.130]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/AES256-SHA; 13 Aug 2019 17:22:20 -0700 Subject: Re: [PATCH net-next] net/ncsi: allow to customize BMC MAC Address offset From: Terry Duncan To: Tao Ren Cc: Andrew Lunn , Jakub Kicinski , "netdev@vger.kernel.org" , "openbmc@lists.ozlabs.org" , Ben Wei , "linux-kernel@vger.kernel.org" , Samuel Mendoza-Jonas , "David S.Miller" , William Kennington References: <20190807002118.164360-1-taoren@fb.com> <20190807112518.644a21a2@cakuba.netronome.com> <20190807184143.GE26047@lunn.ch> <806a76a8-229a-7f24-33c7-2cf2094f3436@fb.com> <20190808133209.GB32706@lunn.ch> <77762b10-b8e7-b8a4-3fc0-e901707a1d54@fb.com> <20190808211629.GQ27917@lunn.ch> <20190808230312.GS27917@lunn.ch> <10079A1AC4244A41BC7939A794B72C238FCE0E03@fmsmsx104.amr.corp.intel.com> <33e3e783-fb93-e628-8baa-a8374540ea25@linux.intel.com> Message-ID: <68c25963-4659-c5a2-f8ca-ee51ae17d63f@linux.intel.com> Date: Tue, 13 Aug 2019 17:22:20 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <33e3e783-fb93-e628-8baa-a8374540ea25@linux.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/13/19 1:54 PM, Terry Duncan wrote: > > On 8/13/19 11:28 AM, Tao Ren wrote: >> On 8/13/19 9:31 AM, Terry Duncan wrote: >>> Tao, in your new patch will it be possible to disable the setting of >>> the BMC MAC?  I would like to be able to send NCSI_OEM_GET_MAC >>> perhaps with netlink (TBD) to get the system address without it >>> affecting the BMC address. >>> >>> I was about to send patches to add support for the Intel adapters >>> when I saw this thread. >>> >>> Thanks, >>> >>> Terry >> >> Hi Terry, >> >> Sounds like you are planning to configure BMC MAC address from user >> space via netlink? Ben Wei started a thread >> "Out-of-band NIC management" in openbmc community for NCSI management >> using netlink, and you may follow up with him for details. >> >> I haven't decided what to do in my v2 patch: maybe using device tree, >> maybe moving the logic to uboot, and I'm also evaluating the netlink >> option. But it shouldn't impact your patch, because you can disable >> NCSI_OEM_GET_MAC option from your config file. > > Thanks Tao. I see now that disabling the NCSI_OEM_GET_MAC option will do > what I want. > > Best, > Terry Hi Tao, After a second look, it appears that the OEM handlers for Broadcom and Melanox in ncsi-rsp.c will set the MAC regardless of the origin of the request. Even with NCSI_OEM_GET_MAC disabled, sending an OEM command with netlink would result in setting the BMC MAC. Thanks, Terry