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 43BAEC433FE for ; Wed, 12 Oct 2022 20:45:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230001AbiJLUpd (ORCPT ); Wed, 12 Oct 2022 16:45:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38636 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229845AbiJLUpD (ORCPT ); Wed, 12 Oct 2022 16:45:03 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 51F0340568; Wed, 12 Oct 2022 13:45:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1665607502; x=1697143502; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=eJJh0s3iMgt2kMH+jx8omA4PulLj6HDFZDLgshKql8s=; b=OOFZa/K5za/rwFe7aaZFPZFPVWWO9sUYj6tV4Q8p0p1lboqjhMmDMINQ z1GUPhIlYaihdGAucBkVaSx+qFVIynnJFCW6A5aXSxkls47ySHnkZeita qtCpT7k6ZctNpQR53n91myiamVPuTwem9zR0nnE6Ic4OmVe1Vhq6bKv/t A1X6h740ychTPLL/zXAt3OIlprRBFziOXe4gTyelqrIIfO9EnhWIL8IhA qYkUM4J18j5lWv92NTHwQMDjYGo9LfeTqUgPi00TidvS1wnlQZcJyRNRL npF8O6Rd2oogquM/wrs6l2bX/hhC7CQ8UGto+CiILznSWTd7UxW627Dq0 g==; X-IronPort-AV: E=McAfee;i="6500,9779,10498"; a="302517887" X-IronPort-AV: E=Sophos;i="5.95,180,1661842800"; d="scan'208";a="302517887" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Oct 2022 13:45:01 -0700 X-IronPort-AV: E=McAfee;i="6500,9779,10498"; a="604697827" X-IronPort-AV: E=Sophos;i="5.95,180,1661842800"; d="scan'208";a="604697827" Received: from agluck-desk3.sc.intel.com ([172.25.222.78]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Oct 2022 13:45:01 -0700 Date: Wed, 12 Oct 2022 13:44:59 -0700 From: Tony Luck To: Borislav Petkov Cc: Serge Semin , Serge Semin , Michal Simek , Mauro Carvalho Chehab , James Morse , Robert Richter , Alexey Malahov , Michail Ivanov , Pavel Parkhomenko , Punnaiah Choudary Kalluri , Manish Narani , Dinh Nguyen , Rob Herring , Krzysztof Kozlowski , Rob Herring , Krzysztof Kozlowski , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RESEND v3 13/17] EDAC/mc: Add MC unique index allocation procedure Message-ID: References: <20220929232712.12202-1-Sergey.Semin@baikalelectronics.ru> <20220929232712.12202-14-Sergey.Semin@baikalelectronics.ru> <20221012200154.7fq3i7igbgkcy2mx@mobilestation> 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-edac@vger.kernel.org On Wed, Oct 12, 2022 at 10:33:35PM +0200, Borislav Petkov wrote: > On Wed, Oct 12, 2022 at 11:01:54PM +0300, Serge Semin wrote: > "A new special MC index is introduced here. It's defined by the > EDAC_AUTO_MC_NUM macro with a value specifically chosen as the least > probable value used for the real MC index. In case if the EDAC_AUTO_MC_NUM > index is specified by the EDAC LLDD, the MC index will be either retrieved > from the MC device OF-node alias index ("mc[:number:]") or automatically > generated as the next-free MC index found by the ID allocation procedure." Just curious.If I have an EDAC driver using EDAC_AUTO_MC_NUM, and I unload and reload the driver a bunch of times. Do I get the same memory controller numbers each reload, or get an ever increasing set each time? -Tony