News: 0001473647

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Intel Granite Rapids Brings New "SBAF" Core Testing Capability

([Intel] 42 Minutes Ago Structural Based Functional Test)


Upcoming Intel Xeon 6 "Granite Rapids" processors will support a new Structural Based Functional Test at Field (SBAF) testing capability to help verify the health of the CPU cores.

The past two years Intel Linux engineers have been developing the [1]In-Field Scan (IFS) driver that since Xeon "Sapphire Rapids" processors has supported a means of help [2]verifying the CPU's health and spotting any silicon defects either prior to commissioning new servers or reaffirming the silicon's health after deployment in an ongoing basis. In-Field Scan is especially valuable for hyperscalers, cloud providers, and others for [3]verifying the health of CPUs via various functional tests that can be carried out on the processor internals at the choosing of the administrator.

With upcoming Intel Granite Rapids server processors, In-Field Scan is being extended to include Structural Based Functional Test at Field (SBAF) testing. Intel Linux engineer Kuppuswamy Sathyanarayanan posted a new set of patches overnight for extending the IFS Linux kernel driver for supporting this SBAF capability. The new [4]patch series confirms SBAF with Granite Rapids and explains:

"This patch series adds support for Structural Based Functional Test at Field (SBAF) in the IFS driver. SBAF is a new type of testing that provides comprehensive core test coverage, complementing existing IFS tests like Scan at Field (SAF) and ArrayBist. Granite Rapids (GNR) is the first platform that supports SBAF.

SBAF mimics the manufacturing screening environment and leverages the same test suite. It makes use of Design For Test (DFT) observation sites and features to maximize coverage in minimum time.

Similar to the SAF test, SBAF isolates the core under test from the rest of the system during execution. Upon completion, the core seamlessly resets to its pre-test state and resumes normal operation. Any machine checks or hangs encountered during the test are confined to the isolated core, preventing disruption to the overall system. Like SAF test, the SBAF test is also divided into multiple batches, and each batch test can take hundreds of milliseconds (100-200 ms) to complete. If such a lengthy interruption is undesirable, it is recommended to relocate the time-sensitive applications to other cores for the duration of the test."

There's still time that we may see these new IFS driver additions ready for mainlining in time for the Linux v6.11 kernel cycle if all goes well.



[1] https://www.phoronix.com/search/In-Field+Scan

[2] https://www.phoronix.com/news/Intel-IFS-Lands-Linux-5.19

[3] https://www.phoronix.com/news/Linux-6.2-x86-Microcode

[4] https://lore.kernel.org/platform-driver-x86/20240627023516.3783454-1-sathyanarayanan.kuppuswamy@linux.intel.com/



phoronix

Slashdot Effect Vaporizes Ganymede
-- Submitted by Dave Finton

In one of the more bizarre consequences of the infamous "Slashdot Effect",
Ganymede, the largest moon in our solar system, was completely and utterly
destroyed when CmdrTaco posted an article about the Hubble Space
Telescope's latest round of images and discoveries.

"It all started when we put up some more info on our web page about
Jupiter and Ganymede," said one NASA guy whom we believe may be in charge
of something. "CmdrTaco got wind of it, and posted it on his site."

According to observers, the webserver promptly exploded thereafter,
damaging the nearby remote control system used to aim and focus the
Hubble's cameras from the ground.

"All of the sudden our controls went wacky!" said one engineer. "The
Hubble then started shooting these death rays all over the universe. One
of those rays hit Ganymede, and *POOF*. There it went! We were all like,
'COOOOOL! Let's aim it something else!'"