From: Dave Hansen <dave.hansen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Rishabh Agrawal <rishabhagr@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
len.brown@intel.com, drake@endlessm.com,
rafael.j.wysocki@intel.com, mingo@redhat.com, tglx@linutronix.de,
vaibhav.shankar@intel.com, biernacki@google.com,
zwisler@google.com, mattedavis@google.com,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Feng Tang <feng.tang@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH v2] Add hardcoded crystal clock for KabyLake
Date: Thu, 20 Oct 2022 10:18:47 -0700 [thread overview]
Message-ID: <3d65c4cc-c002-9e6a-c6ea-fd776968a178@intel.com> (raw)
In-Reply-To: <Y1GBtjcetPpTq0V3@hirez.programming.kicks-ass.net>
On 10/20/22 10:13, Peter Zijlstra wrote:
> And why, pray *WHY* can't Intel simply write the correct information in
> CPUID leaf 15h. I mean, they defined the leaf, might as well use it, no?
Is the data that's in the leaf just wrong? Doesn't that mean that the
CPUID leaf on these models is violating the architecture contract? That
sounds like something that deserves an erratum.
Is there a documented erratum?
next prev parent reply other threads:[~2022-10-20 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 19:01 [PATCH v2] Add hardcoded crystal clock for KabyLake Rishabh Agrawal
2022-10-20 17:13 ` Peter Zijlstra
2022-10-20 17:18 ` Dave Hansen [this message]
2022-11-14 22:58 ` Thomas Gleixner
2022-12-21 22:35 ` Christian A. Ehrhardt
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=3d65c4cc-c002-9e6a-c6ea-fd776968a178@intel.com \
--to=dave.hansen@intel.com \
--cc=biernacki@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=drake@endlessm.com \
--cc=feng.tang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mattedavis@google.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rishabhagr@chromium.org \
--cc=tglx@linutronix.de \
--cc=vaibhav.shankar@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox