Received: by 2002:a05:6358:111d:b0:dc:6189:e246 with SMTP id f29csp809590rwi; Mon, 31 Oct 2022 07:50:07 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6WtHEPF2blEPXnYZQ+cUlqUupSvs2HJlYj6mglTh05OHFzPaNIbvMIHuYtsh5JE+e0rx/S X-Received: by 2002:a63:fd57:0:b0:43c:9a42:74fb with SMTP id m23-20020a63fd57000000b0043c9a4274fbmr12854611pgj.174.1667227807200; Mon, 31 Oct 2022 07:50:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1667227807; cv=none; d=google.com; s=arc-20160816; b=wk6TzLUYaJ5xXnZlbZ9AMPEPjGxMFfdMsjJLmDUZR1EedWt5QtFLrjCpBxPGz+U8Gd zHieIKiO1bmeUExXtakFtreRiOSctTgX8ti22YrO5AD3BPnjf19gmBAp63cvfBkwnb25 rBqlVLkQCViGOHIKTZlEDKNAMaGWcamUEv5/baxGnaFhKRaGMJdH8pns4YfYi2rry/ah gTpVlZIAGWVgyK+iGDSJ3pFvWUeYKyb+tcU61qVbfnKILjocppZ/tBi8G2AphcJ9FKAi jBCYs69F9o4Q1SKQUKz8uEx+GrFrrcfUqUBq4TfzXQTUKZPbIxAw09zUL3AXJjWyMYP/ cbeA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=m3rS7ZOPDHRvZr3V/vvpo/qbENUpvRcqo7cok3v2x3M=; b=R5OvpcwG130SiR5JrYSIzXml/CnpIrT+wbbMRgQN39cZ/nEiQRX1C2Iuh/N5YwfzUx jVHRdx+VgRnvU1wEES5P/nG/Y07A63yj5D6jUe5iEYkFEye9w4gDPpD2aminfSHtJMSX UJ2SpMKVm0g3QevV05SbJFmyBfx5F+Owr1USH362/iNG+3U8qtl2lBFshmxS6azr8BT+ XZ3RRMG/SROcjaBt6DnnQxTK/h0KoW724qBOmY4SFS3nLXfDjZXQngiy4hRmM7I5/akz bgVPOVlR5izUiCxcxKZ7dUC8QSLr0ZlinUkp6ywvn6PvxP8ebtBo5DWaJXXzffwF3boe 5DPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=r8LV6uPM; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l9-20020a170903120900b00186e9ad55c1si9173486plh.434.2022.10.31.07.49.52; Mon, 31 Oct 2022 07:50:07 -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=@google.com header.s=20210112 header.b=r8LV6uPM; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231663AbiJaOnF (ORCPT + 99 others); Mon, 31 Oct 2022 10:43:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54500 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231658AbiJaOnD (ORCPT ); Mon, 31 Oct 2022 10:43:03 -0400 Received: from mail-yw1-x1136.google.com (mail-yw1-x1136.google.com [IPv6:2607:f8b0:4864:20::1136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6C4ECD64 for ; Mon, 31 Oct 2022 07:43:02 -0700 (PDT) Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-367cd2807f2so109902817b3.1 for ; Mon, 31 Oct 2022 07:43:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=m3rS7ZOPDHRvZr3V/vvpo/qbENUpvRcqo7cok3v2x3M=; b=r8LV6uPMuGeqnZjOBbU15rihGbvXAwsvKBQMb/ILfmao522fVg4IoF8LZUv4NZyDe2 DhsN5OAGOch/lo40i5h940Z3gVaD3a7KbTlMZjYcs8G8R/nulskq60DE0GljodLCnanR JtmLOg8rgSNzh04aCRJproQwwZxCnHkkmLOPV7BGDK2p/OCfFburo2y04z0ucphvOyjJ P5jcSq3L1lFdAHpPYT7oo1SaSFDp2DDK43jdt5KEXUgnZSCUGabIii5NduLyTMPHNHMa Lwun+VK4xq+vsU7k6j/g9wLi81RIB412ACwOnzvEoOmT4kvq8J7bp8e0FSogizDwqlUU SBng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=m3rS7ZOPDHRvZr3V/vvpo/qbENUpvRcqo7cok3v2x3M=; b=1M+bHIndkJXCSpxKpQP7TXZ3la15iMJtJX039+Tdu6VOh25tgmiUKHyCUkq4d0KL6y 6NKtK9CiVvOK6c/kxQ0iaVo/IBfRU8YJ4N/0vroVxQwXgdPdTQX8TiqeHoMGECfQZEDT J89s+xry9d+bf/6HnUljQT1RSJJLaRw/Fp0ozCRjaVJ0Du+uvp6ETN4mqdSZDnHt30K4 vXTlqV6qnj26CvWTLTSBxPmx0188NforNheaUeEcNU9Shd6TlgtUfdgwrwNZ9EnOVGoF QyBuFrAhkMID4s06zmsKcrj0jdC37zN91TeHAjjBWfZ/BRd8x/jIV+semH2AzPFnEHYZ KiDw== X-Gm-Message-State: ACrzQf38BGzTvcogJcYoThVhJZGbM4J1uAFP3fo+yQHOIVGfSieTXrGU 9elRZxDDbrNB3ZG5M4sNjAf1WptKk0v4qrEhN9WCiA== X-Received: by 2002:a0d:eec4:0:b0:361:3052:476f with SMTP id x187-20020a0deec4000000b003613052476fmr12831988ywe.185.1667227381609; Mon, 31 Oct 2022 07:43:01 -0700 (PDT) MIME-Version: 1.0 References: <20221021131204.5581-1-james.morse@arm.com> <20221021131204.5581-2-james.morse@arm.com> In-Reply-To: <20221021131204.5581-2-james.morse@arm.com> From: Peter Newman Date: Mon, 31 Oct 2022 15:42:50 +0100 Message-ID: Subject: Re: [PATCH 01/18] x86/resctrl: Track the closid with the rmid To: James Morse Cc: x86@kernel.org, linux-kernel@vger.kernel.org, Fenghua Yu , Reinette Chatre , Thomas Gleixner , Ingo Molnar , Borislav Petkov , H Peter Anvin , Babu Moger , shameerali.kolothum.thodi@huawei.com, D Scott Phillips OS , carl@os.amperecomputing.com, lcherian@marvell.com, bobo.shaobowang@huawei.com, tan.shaopeng@fujitsu.com, Jamie Iles , Xin Hao , xingxin.hx@openanolis.org, baolin.wang@linux.alibaba.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL 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 Hi James, On Fri, Oct 21, 2022 at 3:12 PM James Morse wrote: > > x86's RMID are independent of the CLOSID. An RMID can be allocated, > used and freed without considering the CLOSID. > > MPAM's equivalent feature is PMG, which is not an independent number, > it extends the CLOSID/PARTID space. For MPAM, only PMG-bits worth of > 'RMID' can be allocated for a single CLOSID. > i.e. if there is 1 bit of PMG space, then each CLOSID can have two > monitor groups. > > To allow rescrl to disambiguate RMID values for different CLOSID, > everything in resctrl that keeps an RMID value needs to know the CLOSID > too. This will always be ignored on x86. I recall that the allocation of RMIDs on MPAM was an open topic of discussion on the other thread. Can we finish that discussion first? https://lore.kernel.org/lkml/14df28f0-90b1-9c43-add5-08947165596d@intel.com/ Thanks! -Peter