mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yipeng Zou <zouyipeng@huawei.com>
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>
Subject: Re: [PATCH stable 0/1] x86: aperfmperf: bug report
Date: Fri, 4 Nov 2022 10:26:01 +0800	[thread overview]
Message-ID: <963da72d-ce85-ea0b-2100-33d191f724ac@huawei.com> (raw)
In-Reply-To: <20221021021740.137196-1-zouyipeng@huawei.com>

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


      parent reply	other threads:[~2022-11-04  2:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  2:17 Yipeng Zou
2022-10-21  2:17 ` [PATCH stable 1/1] x86: aperfmperf: fix overflow problem in the concurrency scenario Yipeng Zou
2022-11-04  2:26 ` Yipeng Zou [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=963da72d-ce85-ea0b-2100-33d191f724ac@huawei.com \
    --to=zouyipeng@huawei.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®