From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hansg@kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: ISST: Avoid model check for recent servers
Date: Thu, 17 Sep 2026 18:04:03 +0300 [thread overview]
Message-ID: <178965744374.22350.4555360742713357018.b4-ty@b4> (raw)
In-Reply-To: <20260818203427.2738209-1-srinivas.pandruvada@linux.intel.com>
On Tue, 18 Aug 2026 13:34:27 -0700, Srinivas Pandruvada wrote:
> To enable SST functions, a CPU model entry is required. This causes
> unnecessary delays in deploying new servers on older kernels.
>
> To avoid this, if no CPU model match is found, allow the SST common
> driver to load, when all of the following conditions are met:
>
> - Not running as a guest.
> - The platform is identified as a server via ACPI PM profile.
> - The CPU belongs to the Intel family 19 (decimal), which starts with
> Diamond Rapids. All recent servers are capable of enumerating SST
> features.
> - MSR_PM_LOGICAL_ID (0x54) is present to retrieve the PM logical ID.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
FYI [if applicable to your patch], as per Linus' policy change, also
fixes are mostly routed through for-next unless the fix is for a
commit introduced in the most recent cycle or is clearly a regression
fix.
The list of commits applied:
[1/1] platform/x86: ISST: Avoid model check for recent servers
commit: 153de724f47af43f0e0a1acc3b1dada18322cd18
--
i.
prev parent reply other threads:[~2026-09-17 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 20:34 Srinivas Pandruvada
2026-09-17 15:04 ` Ilpo Järvinen [this message]
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=178965744374.22350.4555360742713357018.b4-ty@b4 \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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
all inboxes | Powered by JetHome®