Intel CEO Lip-Bu Tan confirmed during the company’s second-quarter 2026 earnings call that simultaneous multithreading—sold as Hyper-Threading—will return to its data-center processors with the Xeon 8 “Coral Rapids” family, scheduled for release in 2028. The announcement reverses a multi-year effort to phase out the technology across server and client product lines and signals that Intel is rethinking how its highest-performance Xeons compete in a market increasingly dominated by massive physical core counts.

What Intel Actually Announced

Tan’s confirmation came in response to a question about Intel’s long-term strategy to regain market share, according to a transcript published by Investing.com. He tied the return of SMT directly to plans for strengthening competitiveness in retail and enterprise CPU segments. TechSpot first reported the news on July 26, noting that the commitment applies specifically to the Xeon 8 “Coral Rapids” P-core generation and that no equivalent pledge has been made for client processors.

The roadmap context makes the reversal clearer. Intel had already disclosed in its Q4 2025 earnings materials that Coral Rapids would reintroduce multithreading to the data-center lineup, but the latest earnings call elevated that technical detail into a public competitive message. The upcoming Xeon 7 “Diamond Rapids” family, expected before Coral Rapids, is widely anticipated to ship without SMT on its performance cores—leaving an SMT gap in Intel’s high-end server portfolio until Coral Rapids arrives.

Coral Rapids itself remains a long-range project. Intel has not released core counts, thread counts per SKU, cache architecture, memory-channel specs, or power envelopes. The only concrete timeline is 2028, which means this announcement is a directional signal rather than an imminent product change.

Why This Matters for Server Deployments

For Windows Server administrators, virtualization teams, and enterprise infrastructure planners, the return of Hyper-Threading to a premium Xeon line will reshape how they think about logical processors, vCPU allocation, and server consolidation.

Virtualization and Mixed Workloads Get a New Lever

A Xeon P-core with two hardware threads per core gives a hypervisor more scheduling flexibility. In environments running Hyper-V, SQL Server, large .NET or Java application estates, or dense container platforms, that extra logical CPU can improve consolidation ratios when workloads don’t uniformly saturate physical cores. A database server that mixes latency-sensitive queries with background maintenance, for example, may see better overall throughput when SMT lets idle execution resources pick up additional work.

The value is not universal. A compute-bound HPC job that stresses every execution unit may run best with one thread per core. A memory-bandwidth-starved workload may gain nothing from more logical CPUs. As Intel’s own Xeon tuning documentation explains, the two logical processors share major execution resources, so gains depend entirely on whether threads complement each other’s demands.

Licensing and Capacity Planning Remain Complex

SMT does not double physical cores for licensing purposes, but many enterprise applications license per core, per socket, or per vCPU. Administrators must distinguish between:

  • Physical cores
  • Logical processors (hardware threads)
  • Assigned vCPUs
  • Licensed core counts
  • Actual application concurrency

A Coral Rapids server that exposes 256 logical CPUs on 128 physical cores will not automatically deliver 256 cores’ worth of performance, nor will it necessarily count as 256 cores under software license rules. IT teams will need to measure performance with SMT on and off in their own stacks and check licensing terms before assuming any cost advantage.

Security Considerations Haven’t Gone Away

Shared microarchitectural resources between sibling threads have been a vector for side-channel attacks. Intel has published guidance on vulnerabilities like SMoTherSpectre and Gather Data Sampling, noting that mitigations exist but may carry performance trade-offs. For Coral Rapids deployments, especially in multi-tenant or confidential-computing setups, the operational rule is straightforward: keep firmware and hypervisor patches current, review Intel’s platform-specific security documentation once hardware ships, and test mitigation impacts. Disabling SMT in firmware remains an option if a workload demands it.

The Road to Coral Rapids: How SMT Fell Out of Favor

Intel introduced Hyper-Threading in 2001 as a way to squeeze more throughput from a single core by exposing two architectural states to the operating system. For two decades it was a hallmark of Xeon branding. The company began backing away from the technology with its hybrid-core era.

  • Alder Lake (2021): Intel’s first desktop hybrid architecture limited Hyper-Threading to Performance-cores; Efficiency-cores stayed single-threaded.
  • Arrow Lake-S (2024): Client CPUs dropped Hyper-Threading entirely.
  • Xeon 6 Granite Rapids (2024): The P-core flagship retained SMT, offering up to 128 cores and 256 threads, but this was positioned as a high-performance outlier.
  • Xeon 6+ Clearwater Forest (2025): Built on Intel’s 18A process, this E-core–only line scaled to 288 single-threaded cores with no SMT, targeting cloud-native scale-out.
  • Xeon 7 Diamond Rapids (expected before 2028): Leaked roadmap details suggest no SMT on P-cores, prioritizing raw physical-core count and per-thread performance.

The shift reflected a belief inside Intel that ever-higher physical core counts could substitute for SMT, particularly in dense E-core designs where power efficiency and predictable per-core behavior matter most. Clearwater Forest, for instance, claims a 17% instructions-per-clock uplift over the prior Sierra Forest while still avoiding SMT’s complexity.

But in P-core Xeons aimed at databases, virtualized environments, and AI-adjacent infrastructure, the market message was mixed. Granite Rapids kept Hyper-Threading, Diamond Rapids apparently omits it, and then Coral Rapids brings it back. That sequence suggests Intel is now deliberately varying SMT by generation to target different competitive windows.

What Windows Server Admins Should Do Now

Coral Rapids won’t arrive until 2028, so there’s no immediate hardware to configure. But the announcement creates a planning signal that IT teams can act on today.

  1. Review your current SMT stance. If your organization runs Xeon servers with SMT enabled, documents its impact on key workloads, and benchmarks performance with and without the feature, you already have a baseline for future comparisons. If not, start collecting that data now on existing Granite Rapids or earlier SMT-equipped systems.

  2. Map virtualization density to thread counts. For Hyper-V and other hypervisors, test how vCPU-to-logical-processor ratios affect responsiveness and utilization in your actual mix of VMs. Coral Rapids may allow more aggressive consolidation in some cases, but only if you understand today’s limits.

  3. Track Intel’s Diamond Rapids transition. Since Diamond Rapids is expected to skip SMT, server refreshes that occur between now and Coral Rapids’ launch will likely face a choice between high physical-core counts without SMT or waiting. Early evaluation of Diamond Rapids vs. existing Granite Rapids will inform that decision.

  4. Engage with software licensing teams. Begin conversations with major application vendors about how they count cores vs. threads, especially for per-core licensed databases and middleware, so you can model Coral Rapids’ cost implications as specs solidify.

  5. Watch for security research. As 2028 approaches, keep an eye on Intel’s security advisories for any new SMT-side-channel disclosures and mitigation options specific to the Coral Rapids architecture.

The Bigger Picture: 2028 and Beyond

Intel’s decision does not mean the company has turned against high core counts. Clearwater Forest proves that massive single-threaded E-cores remain central to its cloud strategy. Rather, Coral Rapids is a bet that the most demanding server workloads—those that justify premium P-cores—will benefit from the combination of strong single-thread performance and the ability to soak up idle core resources with a second thread.

What remains unclear is whether the technology will ever return to client processors. Laptops and desktops face different thermal, power, and hybrid-architecture constraints that make SMT’s value harder to justify. Intel’s silence on that front suggests Coral Rapids is, for now, strictly a data-center play.

The competitive impact will hinge on execution. If Coral Rapids emerges in 2028 with a compelling balance of per-core speed, thread capacity, and platform features, it could strengthen Intel’s hand against AMD’s EPYC and Arm-based server chips. If delays or underwhelming performance erode that promise, the SMT revival may prove to be a footnote. For infrastructure planners, the takeaway is clear: logical threads are returning to Intel’s premium server roadmap, and they’re worth preparing for—but not before 2028.