All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Radoslaw Biernacki <biernacki@google.com>,
	Paul Menzel <pmenzel@molgen.mpg.de>
Cc: x86@kernel.org, Ross Zwisler <zwisler@google.com>,
	Daniel Drake <drake@endlessm.com>,
	Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
	"H . Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Len Brown <len.brown@intel.com>,
	Linux Upstreaming Team <linux@endlessm.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	Thorsten Leemhuis <regressions@leemhuis.info>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/tsc: Use hard-coded crystal clock for Skylake mobile
Date: Mon, 11 May 2020 14:34:41 +0200	[thread overview]
Message-ID: <87y2py6466.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAM4=Rn+7RGHEGa7u33zUA0b-cBehadw4NKN75JtjKjOhxm2Fxg@mail.gmail.com>

Radoslaw Biernacki <biernacki@google.com> writes:
> We found that regression only on specific SKU which was used in one
> model of ChromeBook.
> What's interesting is that some other SKU is fine.
>
> The consequences of this are rather not trivial,
> so this was considered a quickfix and temporary till we develop
> something better.
> In contrast to ChromeOs, I know that there is no way of finding if
> there are in fact regressions on generic kernel in the field (this is
> SKU dependent),
> but we also think that this problem should be addressed in a better
> way (if possible).

Fix the BIOS to setup the CPUID/MSRs correctly?

Thanks,

        tglx

  reply	other threads:[~2020-05-11 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200509113717.9084-1-pmenzel@molgen.mpg.de>
     [not found] ` <87eerr3ppb.fsf@nanos.tec.linutronix.de>
2020-05-11  7:38   ` [PATCH] x86/tsc: Use hard-coded crystal clock for Skylake mobile Paul Menzel
2020-05-11  8:45     ` Radoslaw Biernacki
2020-05-11 12:34       ` Thomas Gleixner [this message]
2020-05-11 15:39         ` Radoslaw Biernacki
2020-05-11  9:36     ` Peter Zijlstra

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=87y2py6466.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=biernacki@google.com \
    --cc=bp@alien8.de \
    --cc=drake@endlessm.com \
    --cc=hpa@zytor.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=rafael.j.wysocki@intel.com \
    --cc=regressions@leemhuis.info \
    --cc=x86@kernel.org \
    --cc=zwisler@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.