On Tue, Aug 06, 2024 at 02:01:55AM +, Michael Kelley wrote:
> From: Wei Liu Sent: Friday, August 2, 2024 4:50 PM
> >
> > On Tue, Jun 11, 2024 at 07:51:48AM -0700, Roman Kisel wrote:
> > >
> > >
> > > On 6/5/2024 7:55 PM, mhkelle...@gmail.com wrote:
> > > > From: Michael Kelley
> > > >
> > >
From: Wei Liu Sent: Friday, August 2, 2024 4:50 PM
>
> On Tue, Jun 11, 2024 at 07:51:48AM -0700, Roman Kisel wrote:
> >
> >
> > On 6/5/2024 7:55 PM, mhkelle...@gmail.com wrote:
> > > From: Michael Kelley
> > >
> > > A Linux guest on Hyper-V gets the TSC frequency from a synthetic MSR, if
> > > a
On Tue, Jun 11, 2024 at 07:51:48AM -0700, Roman Kisel wrote:
>
>
> On 6/5/2024 7:55 PM, mhkelle...@gmail.com wrote:
> > From: Michael Kelley
> >
> > A Linux guest on Hyper-V gets the TSC frequency from a synthetic MSR, if
> > available. In this case, set X86_FEATURE_TSC_KNOWN_FREQ so that Linux
On 6/5/2024 7:55 PM, mhkelle...@gmail.com wrote:
From: Michael Kelley
A Linux guest on Hyper-V gets the TSC frequency from a synthetic MSR, if
available. In this case, set X86_FEATURE_TSC_KNOWN_FREQ so that Linux
doesn't unnecessarily do refined TSC calibration when setting up the TSC
clocks
From: Michael Kelley
A Linux guest on Hyper-V gets the TSC frequency from a synthetic MSR, if
available. In this case, set X86_FEATURE_TSC_KNOWN_FREQ so that Linux
doesn't unnecessarily do refined TSC calibration when setting up the TSC
clocksource.
With this change, a message such as this is no
