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;
Message-ID: <963da72d-ce85-ea0b-2100-33d191f724ac@huawei.com>
Date:   Fri, 4 Nov 2022 10:26:01 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.0.3
Subject: Re: [PATCH stable 0/1] x86: aperfmperf: bug report
To:     <tglx@linutronix.de>, <bp@alien8.de>, <mingo@redhat.com>,
        <x86@kernel.org>, <hpa@zytor.com>, <rafael.j.wysocki@intel.com>,
        <linux-kernel@vger.kernel.org>
References: <20221021021740.137196-1-zouyipeng@huawei.com>
Content-Language: en-US
From:   Yipeng Zou <zouyipeng@huawei.com>
In-Reply-To: <20221021021740.137196-1-zouyipeng@huawei.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

Ping~

在 2022/10/21 10:17, Yipeng Zou 写道:
> Recently i was doing some work about calculating CPU frequency on x86 on
> stable branch linux-5.10.y, and there is a problem which i descrip in
> the commit message.
>
> I've noticed that it has been abandoned on the mainline. On the mainline
> it becomes to update [a,m]cnt in timer code with HZ frequency, and it is
> actually calculated at the time of reading the cpu freqency. This solves
> the problem above.
>
> So, Are there other reasons why the stable branch doesn't have these
> changes?, this patch is just to ask how we plan to fix it.
>
> Yipeng Zou (1):
>    x86: aperfmperf: fix overflow problem in the concurrency scenario
>
>   arch/x86/kernel/cpu/aperfmperf.c | 4 ----
>   1 file changed, 4 deletions(-)
>
-- 
Regards,
Yipeng Zou