Received: by 2002:a05:7412:2a8c:b0:e2:908c:2ebd with SMTP id u12csp2233562rdh; Tue, 26 Sep 2023 17:39:34 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEVBgO5l1fFKV+s+kqw0e8e6sqFYtksvumbag9jdjX78RxVcA+4y1GWo82VJDDfNNF9b1SQ X-Received: by 2002:a17:90a:1fc7:b0:26d:1f75:7fa3 with SMTP id z7-20020a17090a1fc700b0026d1f757fa3mr266416pjz.4.1695775174055; Tue, 26 Sep 2023 17:39:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695775174; cv=none; d=google.com; s=arc-20160816; b=UaAnOFp/R+zb0pwu9x/7o5RzB+3zR4HcrPULvxbND0fGif2nAJPs+MHIDvBcEsgc0w SSOeCub0Nqnld1tw6I4aUCY6tExIajbQzDxSCePNmMRvMAaPJMPzahtpyNFH6MPK+oZK OfVm8Szxg9faRl8wDPeINB3s4XgudLt+FZU8PbDBKo9MLTu9UWJkDNUbNeOyl+SATJmw AuU3YTwlPzwWVW8x2WyOELGoqwRXd5UZQz8Rt0llIYBiYOVLI5EW/J2fF6ZbOsrimctV s6aQqEQXOt4872YxvGf6924Jr7ojb1Mj+7cJkExlQm1W5LIKQ26a9pUlkYSzfmozUraQ ZtxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=txi09+M9nIcP7oQJ22VKdeHHF+OydMHmqueQ6Cjgyfw=; fh=AESVLwR11kHuzSrfc2lzUY8Iibgw2QcUWqRJ5cRpxRk=; b=Rydshfdg3CuItdlo6Leiqw2nvaH9kUd2byuMUhxXLMeqS8Ja23IYoq+JsDReMSGqsq tQlBXsBAPwEKn4WU0PWlyT1w2VkJkPsrg/1+PotOI0iK1q19QtiHRt7AY5qRlDCvYPBJ fV9Elxd2SLZ5iAbNjs4ACJRW87tuBOXEP1IVjDs3rx75pIsfwnFFUnKBPShkV0ltgfHQ P/7tXSTdTVgWXkZF7YXGvP9ae88lli02o8QbuIMafxUYpVwqwH7ddiU303blLnSL/GQX 4E4firCoXUXbgTWqQIyq/GLWoAiMr7zv6PwecZBqxq3WZNdPyXDUecN/QmScFB0PTfeu t47w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Gq6PY16U; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 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 lipwig.vger.email (lipwig.vger.email. [23.128.96.33]) by mx.google.com with ESMTPS id r13-20020a17090b050d00b00276d4b6009asi14742975pjz.135.2023.09.26.17.39.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Sep 2023 17:39:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Gq6PY16U; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by lipwig.vger.email (Postfix) with ESMTP id 46A368246E30; Tue, 26 Sep 2023 10:23:34 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at lipwig.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233644AbjIZRXa (ORCPT + 99 others); Tue, 26 Sep 2023 13:23:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56248 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232053AbjIZRX2 (ORCPT ); Tue, 26 Sep 2023 13:23:28 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 60E55180; Tue, 26 Sep 2023 10:23:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1695749002; x=1727285002; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=qjVC/s4j7SxQRGeSzIg7naJ8oHI9PB59wRQgY2RtkPE=; b=Gq6PY16UWxKVSSvV5/9Oh9wXMb/Tk7I/EsLqoPWGppz/RUQMt8/FLnmX DKnNKJOPpPy06ucDcbGexVuQjHJfmpjrKQiQOP/J6NZ2C5djUkDgTyqVP ET7qEeu66QeQBHDFH0w8RC8FqbaU7CIjZVUKlQRYhTyD4O+W1yK/Tzv4N w9AHvvfpqg3tvnWdTrdJM4zrAZf2KTAP99k0tJ3FsDQC/JmeZ7rO6d2S9 saM2NUmqza2BvdbGzT7ZgLkCK2IKYI7staLqWcu08v1iMUEbiPm8E/llj b1B+umLtG3xZ0XLFXO9E3Aa/nQv0000BQNrzh6BkE5SKz66grtCmAziRO Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10845"; a="381520625" X-IronPort-AV: E=Sophos;i="6.03,178,1694761200"; d="scan'208";a="381520625" Received: from orviesa001.jf.intel.com ([10.64.159.141]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Sep 2023 10:21:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.03,178,1694761200"; d="scan'208";a="235632" Received: from lkp-server02.sh.intel.com (HELO 32c80313467c) ([10.239.97.151]) by orviesa001.jf.intel.com with ESMTP; 26 Sep 2023 10:21:23 -0700 Received: from kbuild by 32c80313467c with local (Exim 4.96) (envelope-from ) id 1qlBkp-0003Ap-2V; Tue, 26 Sep 2023 17:21:48 +0000 Date: Wed, 27 Sep 2023 01:21:36 +0800 From: kernel test robot To: Lukasz Luba , linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, rafael@kernel.org Cc: oe-kbuild-all@lists.linux.dev, lukasz.luba@arm.com, dietmar.eggemann@arm.com, rui.zhang@intel.com, amit.kucheria@verdurent.com, amit.kachhap@gmail.com, daniel.lezcano@linaro.org, viresh.kumar@linaro.org, len.brown@intel.com, pavel@ucw.cz, mhiramat@kernel.org, qyousef@layalina.io, wvw@google.com Subject: Re: [PATCH v4 11/18] PM: EM: Add runtime update interface to modify EM power Message-ID: <202309270106.c56Z2Tci-lkp@intel.com> References: <20230925081139.1305766-12-lukasz.luba@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230925081139.1305766-12-lukasz.luba@arm.com> X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lipwig.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (lipwig.vger.email [0.0.0.0]); Tue, 26 Sep 2023 10:23:34 -0700 (PDT) Hi Lukasz, kernel test robot noticed the following build warnings: [auto build test WARNING on rafael-pm/linux-next] [also build test WARNING on rafael-pm/thermal linus/master v6.6-rc3 next-20230926] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Lukasz-Luba/PM-EM-Add-missing-newline-for-the-message-log/20230925-181243 base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next patch link: https://lore.kernel.org/r/20230925081139.1305766-12-lukasz.luba%40arm.com patch subject: [PATCH v4 11/18] PM: EM: Add runtime update interface to modify EM power config: i386-randconfig-063-20230926 (https://download.01.org/0day-ci/archive/20230927/202309270106.c56Z2Tci-lkp@intel.com/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230927/202309270106.c56Z2Tci-lkp@intel.com/reproduce) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot | Closes: https://lore.kernel.org/oe-kbuild-all/202309270106.c56Z2Tci-lkp@intel.com/ sparse warnings: (new ones prefixed by >>) kernel/power/energy_model.c:125:13: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct em_perf_table *tmp @@ got struct em_perf_table [noderef] __rcu *runtime_table @@ kernel/power/energy_model.c:125:13: sparse: expected struct em_perf_table *tmp kernel/power/energy_model.c:125:13: sparse: got struct em_perf_table [noderef] __rcu *runtime_table >> kernel/power/energy_model.c:613:27: sparse: sparse: incompatible types in comparison expression (different address spaces): >> kernel/power/energy_model.c:613:27: sparse: struct em_perf_table [noderef] __rcu * >> kernel/power/energy_model.c:613:27: sparse: struct em_perf_table * vim +613 kernel/power/energy_model.c 569 570 /** 571 * em_dev_unregister_perf_domain() - Unregister Energy Model (EM) for a device 572 * @dev : Device for which the EM is registered 573 * 574 * Unregister the EM for the specified @dev (but not a CPU device). 575 */ 576 void em_dev_unregister_perf_domain(struct device *dev) 577 { 578 struct em_perf_table __rcu *runtime_table; 579 struct em_perf_domain *pd; 580 581 if (IS_ERR_OR_NULL(dev) || !dev->em_pd) 582 return; 583 584 if (_is_cpu_device(dev)) 585 return; 586 587 pd = dev->em_pd; 588 /* 589 * The mutex separates all register/unregister requests and protects 590 * from potential clean-up/setup issues in the debugfs directories. 591 * The debugfs directory name is the same as device's name. 592 * The lock also protects the updater of the runtime modifiable 593 * EM and this remover. 594 */ 595 mutex_lock(&em_pd_mutex); 596 597 em_debug_remove_pd(dev); 598 599 runtime_table = pd->runtime_table; 600 601 /* 602 * Safely destroy runtime modifiable EM. By using the call 603 * synchronize_rcu() we make sure we don't progress till last user 604 * finished the RCU section and our update got applied. 605 */ 606 rcu_assign_pointer(pd->runtime_table, NULL); 607 synchronize_rcu(); 608 609 /* 610 * After the sync no updates will be in-flight, so free the 611 * memory allocated for runtime table (if there was such). 612 */ > 613 if (runtime_table != pd->default_table) { -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki