linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Andy Shevchenko' <andy.shevchenko@gmail.com>,
	Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andy@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Vipul Kumar <vipulk0511@gmail.com>,
	Vipul Kumar <vipul_kumar@mentor.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Srikanth Krishnakar <Srikanth_Krishnakar@mentor.com>,
	Cedric Hombourger <Cedric_Hombourger@mentor.com>,
	Len Brown <len.brown@intel.com>,
	Rahul Tanwar <rahul.tanwar@linux.intel.com>,
	Tony Luck <tony.luck@intel.com>,
	"Gayatri Kammela" <gayatri.kammela@intel.com>,
	"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stable <stable@vger.kernel.org>
Subject: RE: [PATCH v3 3/3] x86/tsc_msr: Make MSR derived TSC frequency more accurate
Date: Mon, 10 Feb 2020 10:08:38 +0000	[thread overview]
Message-ID: <7486ebeb98bd44d4a50fb6f2df4799df@AcuMS.aculab.com> (raw)
In-Reply-To: <CAHp75VcEKS_XkdfqnydF3KgeH=Fk_9GyQfcmrs6D9rJbTuKstw@mail.gmail.com>

From: Andy Shevchenko
> Sent: 07 February 2020 22:12
> On Fri, Feb 7, 2020 at 10:55 PM Hans de Goede <hdegoede@redhat.com> wrote:
> >
> > The "Intel 64 and IA-32 Architectures Software Developer’s Manual
> > Volume 4: Model-Specific Registers" has the following table for the
> > values from freq_desc_byt:
> 
> For the LGM people in Cc list. Hans included you in order to confirm
> what's going on with TSC on LGM SoC.
> Can you do it in a way that we certainly know clocks with good
> precision (and if Spread Spectrum is in use what should we put here)?

Isn't 'Spread Spectrum' just a scam so that the resonant detector
used by the test equipment fails to register anything?

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  reply	other threads:[~2020-02-10 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 20:54 [PATCH v3 1/3] x86/tsc_msr: Use named struct initializers Hans de Goede
2020-02-07 20:54 ` [PATCH v3 2/3] x86/tsc_msr: Fix MSR_FSB_FREQ mask for Cherry Trail devices Hans de Goede
2020-02-07 20:54 ` [PATCH v3 3/3] x86/tsc_msr: Make MSR derived TSC frequency more accurate Hans de Goede
2020-02-07 22:11   ` Andy Shevchenko
2020-02-10 10:08     ` David Laight [this message]
2020-02-08  0:05   ` Thomas Gleixner
2020-02-23 13:55     ` Hans de Goede

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=7486ebeb98bd44d4a50fb6f2df4799df@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=Cedric_Hombourger@mentor.com \
    --cc=Srikanth_Krishnakar@mentor.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@infradead.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=gayatri.kammela@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rahul.tanwar@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=vipul_kumar@mentor.com \
    --cc=vipulk0511@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).