From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0CB392BD5BB; Mon, 10 Nov 2025 17:33:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762795987; cv=none; b=etxMNgiRBHLGVDmR5DO4Hqq5FgmP0vnd0Yx2hKHjUh/qV1PJS+xzTkfswNhx6uEQ45DBD6bCacK2Zpr8SLYE+pCsJAZCOnyZf5Ur8DKLbwkKK6n7MKlihL06W6o0hkcs0E5rzoccJP/LMp1WlCeqanqajfIEl0HVaOzifiDSXgg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762795987; c=relaxed/simple; bh=+ioVOSVIuUepgxPqJLEvdqtOshMKKOA7Bhlo9YbhNZg=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=knp52LwDUEvMxyoaktAs/2RVraVeH7T2KnKEdoHQGHNIVYpoD6K4a9rgRAatGXr1cv+unBBR26E6fQ96dG7NU80lMkZbNPX7YWXbzhwrnRBpBDPI6o58aMEaAsuOKXdnl/sBNDbMw/g676VP8kNcdmS1W8tcQsNsgANf984mwV0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4d4xZ84c61zJ46bj; Tue, 11 Nov 2025 01:32:32 +0800 (CST) Received: from dubpeml100005.china.huawei.com (unknown [7.214.146.113]) by mail.maildlp.com (Postfix) with ESMTPS id 3540314027A; Tue, 11 Nov 2025 01:33:02 +0800 (CST) Received: from localhost (10.203.177.15) by dubpeml100005.china.huawei.com (7.214.146.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Mon, 10 Nov 2025 17:33:00 +0000 Date: Mon, 10 Nov 2025 17:32:59 +0000 From: Jonathan Cameron To: Ben Horgan CC: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , Zeng Heng Subject: Re: [PATCH 28/33] arm_mpam: Consider overflow in bandwidth counter state Message-ID: <20251110173259.00002c88@huawei.com> In-Reply-To: <20251107123450.664001-29-ben.horgan@arm.com> References: <20251107123450.664001-1-ben.horgan@arm.com> <20251107123450.664001-29-ben.horgan@arm.com> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-acpi@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: lhrpeml500011.china.huawei.com (7.191.174.215) To dubpeml100005.china.huawei.com (7.214.146.113) On Fri, 7 Nov 2025 12:34:45 +0000 Ben Horgan wrote: > Use the overflow status bit to track overflow on each bandwidth counter > read and add the counter size to the correction when overflow is detected. > > This assumes that only a single overflow has occurred since the last read > of the counter. Overflow interrupts, on hardware that supports them could > be used to remove this limitation. > > Cc: Zeng Heng > Signed-off-by: Ben Horgan Reviewed-by: Jonathan Cameron