Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp890053pxb; Wed, 27 Oct 2021 14:33:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwa1xLZtU4zkSfp/rW91vRuE7KLpuJf1YGXTjJdt0cweR+T9Srq9HuGOeq0Pz+gXT0j9kN4 X-Received: by 2002:a50:e004:: with SMTP id e4mr537172edl.246.1635370382848; Wed, 27 Oct 2021 14:33:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635370382; cv=none; d=google.com; s=arc-20160816; b=RjINEML0g012D0Zq/TkgVxVP3CEnCpGdUlvY4uLcMU2MJrGs6+yueXOnmz/XifdWvo e6a0AklyTz+ao2+MmK9RxLprOBgtlsd31+BXvH1Y988OMJCKmUDbLqjPjH42kx+G1zvj VuqO2zGOabNJyZpSWP/nQSuEkAdb5gLdvOHUx8t+YodNNlIQ6sReEYbAD8fKlcbTtD0o kZ7K8dxi/mzW6bCojcHx+SKX2Jhrv5yVabkDN0dAZWhNwxGpIKRQNKt4BdXrtm8T3LZo lISMhE+zzEU5Hckwvd8XQ236bsR1rN7GMMqxQPWbDKgnCnRwtc/spsr7riDQtmTJ7AL3 +rMg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=+YP5qbjFgwF3i25M6iLD4YZehxnNcnAtp+y0hJlVB3U=; b=w2rPzPCU68eQii1nQq6XzW/jsCOoT+sDo50THLBzpxA+4uFpjFPoSUIqdrYiv1Tcru c+oUP0Uz5+GWQ3EIf9F1eU2LVv8ubnfZ2B9OR76lV4jsOl0M3zt37B1qMJoKUEGFTjrR 5Qyb7jGoifMWuT+uc+YisylUVSxDhYLEYwpzrlQC2XeA9nXMCkDYyFzc2OJvajviockm QrLEfLpvP01GntQCCFNPu3w4lGwESdo1jCjWckUj0YLaFJx/U93qgO5d6FjDgfGARVKe WaVMk6J0oFz34mbaZm2F0uS9sv8S8iWycbU46ESqailD9L76YSwSH8p0elVAOlEFufl5 uFwQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w7si1817168edd.351.2021.10.27.14.32.40; Wed, 27 Oct 2021 14:33:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242899AbhJ0QwR (ORCPT + 97 others); Wed, 27 Oct 2021 12:52:17 -0400 Received: from foss.arm.com ([217.140.110.172]:45312 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229518AbhJ0QwQ (ORCPT ); Wed, 27 Oct 2021 12:52:16 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 4165DED1; Wed, 27 Oct 2021 09:49:50 -0700 (PDT) Received: from [10.1.196.31] (eglon.cambridge.arm.com [10.1.196.31]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 6489A3F70D; Wed, 27 Oct 2021 09:49:48 -0700 (PDT) Subject: Re: [PATCH v2 09/23] x86/resctrl: Switch over to the resctrl mbps_val list To: Reinette Chatre , x86@kernel.org, linux-kernel@vger.kernel.org Cc: Fenghua Yu , Thomas Gleixner , Ingo Molnar , Borislav Petkov , H Peter Anvin , Babu Moger , shameerali.kolothum.thodi@huawei.com, Jamie Iles , D Scott Phillips OS , lcherian@marvell.com, bobo.shaobowang@huawei.com, tan.shaopeng@fujitsu.com References: <20211001160302.31189-1-james.morse@arm.com> <20211001160302.31189-10-james.morse@arm.com> From: James Morse Message-ID: <8dbfa092-685d-dc74-b8e5-449ad0ab5222@arm.com> Date: Wed, 27 Oct 2021 17:49:47 +0100 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Reinette, On 15/10/2021 23:26, Reinette Chatre wrote: > On 10/1/2021 9:02 AM, James Morse wrote: >> Updates to resctrl's software controller follow the same path as >> other configuration updates, but they don't modify the hardware state. >> rdtgroup_schemata_write() uses parse_line() and the resource's >> ctrlval_parse function to stage the configuration. > > parse_ctrlval ? > >> resctrl_arch_update_domains() then updates the mbps_val[] array >> instead, and resctrl_arch_update_domains() skips the rdt_ctrl_update() >> call that would update hardware. >> >> This complicates the interface between resctrl's filesystem parts >> and architecture specific code. It should be possible for mba_sc >> to be completely implemented by the filesystem parts of resctrl. This >> would allow it to work on a second architecture with no additional code. >> >> Change parse_bw() to write the configuration value directly to the >> mba_sc[] array in the domain structure. Change rdtgroup_schemata_write() > > mpbs_val[] array? > >> to skip the call to resctrl_arch_update_domains(), meaning all the >> mba_sc specific code in resctrl_arch_update_domains() can be removed. >> On the read-side, show_doms() and update_mba_bw() are changed to read >> the mba_sc[] array from the domain structure. With this, > > mbps_val[] ? > > Should rdtgroup_size_show() also get a similar snippet? Yes! Good catch! Thanks, James