From: Fei Li <fei1.li@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<peterz@infradead.org>, <dave.hansen@intel.com>,
<gregkh@linuxfoundation.org>, <tglx@linutronix.de>,
<mingo@redhat.com>, <dave.hansen@linux.intel.com>,
<hpa@zytor.com>, <Yu1.Wang@intel.com>, <conghui.chen@intel.com>,
<fengwei.yin@intel.com>, <junjie.mao@intel.com>
Subject: Re: [PATCH v2] x86/acrn: Set X86_FEATURE_TSC_KNOWN_FREQ
Date: Mon, 14 Nov 2022 16:14:25 +0800 [thread overview]
Message-ID: <Y3H44Rdi5ari6fql@louislifei-OptiPlex-7090> (raw)
In-Reply-To: <Y2kkk+XqBP3u6ObI@zn.tnic>
On 2022-11-07 at 16:30:27 +0100, Borislav Petkov wrote:
> On Tue, Nov 01, 2022 at 01:30:19PM +0800, Fei Li wrote:
> > If the TSC frequency is known from the acrn_get_tsc_khz(),
> > the TSC frequency does not need to be recalibrated.
Hi Borislav
Thanks for your comments. So sorry to reply you late.
>
> What if the HV has unstable TSCs? How do you handle that?
>
ACRN hypervisor assumes:
a) The TSC runs at a constant rate in all ACPI P-, C-. and T-states (i.e. invariant TSC)
b) The invariant TSC is based on only one invariant timekeeping hardware (called
Always Running Timer or ART). ACRN main target uses for IoT devices
which are typically one-socket
c) ACRN lives with temperature influence on TSC frequency
> > Avoiding recalibration by setting X86_FEATURE_TSC_KNOWN_FREQ.
>
> Pls read section "2) Describe your changes" in
> Documentation/process/submitting-patches.rst for more details on how to
> write your commit message.
OK, will refine the commit message in v3. Thanks.
>
> > This patch also removes `inline` for acrn_get_tsc_khz() since
> > it doesn't make sense.
>
> Avoid having "This patch" or "This commit" in the commit message. It is
> tautologically useless.
>
> Also, do
>
> $ git grep 'This patch' Documentation/process
>
> for more details.
OK. Thanks.
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-11-14 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 5:30 Fei Li
2022-11-07 10:01 ` Fei Li
2022-11-07 15:30 ` Borislav Petkov
2022-11-14 8:14 ` Fei Li [this message]
2022-11-21 7:52 ` Li, Fei1
2022-11-21 9:33 ` Borislav Petkov
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=Y3H44Rdi5ari6fql@louislifei-OptiPlex-7090 \
--to=fei1.li@intel.com \
--cc=Yu1.Wang@intel.com \
--cc=bp@alien8.de \
--cc=conghui.chen@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fengwei.yin@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=junjie.mao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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®