The European Commission has re-imposed a fine of about $400 million on chipmaker Intel for abusing its dominant position in the x86 processor market. The move is the latest twist in an antitrust saga that has been now running for more than two decades. The Register: According to the Commission, the fine is in response to previously established anticompetitive practices by the silicon giant, aimed at excluding competitors from the market in breach of EU competition rules. The original fine handed to Intel in 2009 was for $1.2 billion, based on findings that the company had given incentives to PC makers to use its CPUs instead of those from rivals, or else delay the launch of specific products containing rival chips.

These incentives consisted of wholly or partially hidden rebates for using Intel chips, or payments in order to delay launching products with rival chips, amounting to so-called "naked restrictions." It ultimately goes back to complaints from rival CPU maker AMD in 2000 and again in 2003 that Intel was engaging in anticompetitive conduct by offering rebates to vendors to favor Intel components. Intel fought the decision, but an appeal by the Silicon Valley outfit to have it overturned was initially denied in 2014. Then in 2022, the EU General Court partially annulled the 2009 ruling by the Commission, in particular the findings related to Intel's conditional rebates, and went on to nix the fine imposed on the company in its entirety.

An anonymous reader quotes a report from 404 Media: Historically, video game preservation efforts usually cover two types of games. The most common are very old or "retro" games from the 16-bit era or earlier, which are trapped on cartridges until they're liberated via downloadable ROMs. The other are games that rely on a live service, like Enter the Matrix's now unplugged servers or whatever games you can only get by downloading them via Nintendo's Wii Shop Channel, which shut down in 2019. But time keeps marching on and a more recent era of games now needs to be attended to if we still want those games to be accessible: indies from the late aughts to mid twenty-teens. That's right. Fez, an icon of the era and indie games scene, is now more than a decade old. And while we don't think of this type of work until we need it, Fez, which most PC players booted on Windows 7 when it first came out, is not going to magically run on your Windows 11 machine today without some maintenance.

The person doing that maintenance, as well as making sure that about 70 of the best known indie games from the same era keep running, is Ethan Lee. He's not as well known as Fez's developer Phil Fish, who was also the subject of the documentary Indie Game: The Movie, but this week Lee started publicly marketing the service he's been quietly providing for over 11 years: maintenance of older games. "The way that I've been pitching it is more of like, the boring infrastructure," he said. "Let's make sure the current build works, whereas a lot of times, people feel like the only way to bring a game into a new generation is to do a big remaster. That's cool, but wouldn't have been cool if Quake II just continued to work between 1997 and now without all the weird stuff in between? That's sort of why I've been very particular about the word maintenance, because it's a continuous process that starts pretty much from the moment that you ship it."

As he explains in his pitch to game developers: "the PC catalog alone has grown very large within the last 15 years, and even small independent studios now have an extensive back catalog of titles that players can technically still buy and play today! This does come at a cost, however: The longer a studio exists, the larger their catalog grows, and as a result, the maintenance burden also grows." Just a few of the other indie games Lee ported include Super Hexagon, Proteus, Rogue Legacy, Dust: An Elysian Tail, TowerFall Ascension, VVVVVV, Transistor, Wizorb, Mercenary Kings, Hacknet, Shenzhen I/O, and Bastion. [...] With the PC, people assume that once a game is on Windows, it can live on forever with future versions of Windows. "In reality, what makes a PC so weird is that there's this big stack of stuff. You have an x86 processor, the current-ish era of like modern graphics processors, and then you have the operating system running on top of that and its various drivers," Lee said. A change to any one of those layers can make a game run badly, or not at all.

Slashdot reader martiniturbide writes: ArcaOS 5.1.0 is an OEM distribution of IBM's discontinued OS/2 Warp operating system. This new version of ArcaOS offers UEFI compatibility allowing it to run in modern x86 hardware and also includes the ability to install to GPT-based disk layouts.

At OS2World the OS/2 community has been called upon to report supported hardware, open source any OS/2 software, make public as much OS/2 documentation as possible and post the important platform links. OS2World insists that open source has helped OS/2 in the past years and it is time to look under the hood to try to clone internal components like Control Program, Presentation Manager, SOM and Workplace Shell.

llvm-mos adapts the popular LLVM compiler to target the MOS 6502 processor (the 1980s microprocessor used in early home computing devices like the Apple II and the Commodore 64). So developer Onno Kortman used it to cross-compile semu, a "minimalist RISC-V system emulator capable of running Linux the kernel and corresponding userland." And by the end of the day, Kortman has Linux running on a Commodore 64.

Long-time Slashdot reader johnwbyrd shared the link to Kortman's repository. Some quotes: "But does it run Linux?" can now be finally and affirmatively answered for the Commodore C64...!

It runs extremely slowly and it needs a RAM Expansion Unit (REU), as there is no chance to fit it all into just 64KiB.

It even emulates virtual memory with an MMU....

The screenshots took VICE a couple hours in "warp mode" (activate it with Alt-W) to generate. So, as is, a real C64 should be able to boot Linux within a week or so.

The compiled 6502 code is not really optimized yet, and it might be realistic to squeeze a factor 10x of performance out of this. Maybe even a simple form of JIT compilation? It should also be possible to implement starting a checkpointed VM (quickly precomputed on x86-64) to avoid the lengthy boot process...

I also tested a minimal micropython port (I can clean it up and post it on github if there is interest), that one does not use the MMU and is almost barely remotely usable with lots of optimism at 100% speed.
A key passage: I have not tested it on real hardware yet, that's the next challenge .. for you. So please send me a link to a timelapse video of an original unit with REU booting Linux :D
Its GitHub repository has build and run instructions...

VMware has joined AMD, Samsung, and members of the RISC-V community to work on an open and cross-platform framework for the development and operation of applications using confidential computing hardware. The Register reports: Revealing the effort at the Confidential Computing Summit 2023 in San Francisco, the companies say they aim to bring about an industry transition to practical confidential computing by developing the open source Certifier Framework for Confidential Computing project. Among other goals, the project aims to standardize on a set of platform-independent developer APIs that can be used to develop or adapt application code to run in a confidential computing environment, with a Certifier Service overseeing them in operation. VMware claims to have researched, developed and open sourced the Certifier Framework, but with AMD on board, plus Samsung (which develops its own smartphone chips), the group has the x86 and Arm worlds covered. Also on board is the Keystone project, which is developing an enclave framework to support confidential computing on RISC-V processors.

Confidential computing is designed to protect applications and their data from theft or tampering by protecting them inside a secure enclave, or trusted execution environment (TEE). This uses hardware-based security mechanisms to prevent access from everything outside the enclave, including the host operating system and any other application code. Such security protections are likely to be increasingly important in the context of applications running in multi-cloud environments, VMware reckons.

Another scenario for confidential computing put forward by Microsoft, which believes confidential computing will become the norm -- is multi-party computation and analytics. This sees several users each contribute their own private data to an enclave, where it can be analyzed securely to produce results much richer than each would have got purely from their own data set. This is described as an emerging class of machine learning and "data economy" workloads that are based on sensitive data and models aggregated from multiple sources, which will be enabled by confidential computing. However, VMware points out that like many useful hardware features, it will not be widely adopted until it becomes easier to develop applications in the new paradigm.

jeditobe writes: ReactOS is an open-source operating system that aims to replicate Microsoft Windows, and can already run many Windows applications without modification. ReactOS published a new (infrequent) newsletter to outline recent work. It reveals that progress has slowed down recently, but the project definitely isn't dead. The newsletter also acknowledges the team hasn't put out a new version since the end of 2021, although progress continues. Due to shifting focuses to quality releases, they are no longer on a quarterly release cadence. The date of the next release is not set yet, but according to a huge list of already-implemented changes they aim for it to be a substantial update.

The last update to ReactOS was version 0.4.14, released on December 2021. While developers were previously committed to releasing updates every three months, that has since changed and updates will now be focused on quality rather than quantity. For the ReactOS team to be confident enough to release something, it needs to have less than 20 known unfixed regressions while adding new features and functions.

Behind the scenes, it looks like things are spinning well. The team specifically highlighted its progress on the x64 port of ReactOS, which went from being a non-booting mess to an operating system that boots up and mostly works. It doesn't run any x86 programs since it doesn't have WoW64, but it's going well.

This week the Linux Foundation shared an update on the Zephyr Project, a small real-time operating system for connected, resource-constrained and embedded devices: The project recently achieved several milestones including surpassing 80,000 commits since it was released in open source in 2015. This is an average of almost 2 commits per hour, which was made recently by 490 individuals, including 166 first-timers, who contributed to the 3.4 release. Zephyr RTOS supports over 450 boards running embedded microcontrollers from Arm and RISC-V to Tensilica, NIOS, ARC and x86 as single and multicore systems...

Zephyr RTOS has a growing set of software libraries that can be used across various applications and industry sectors such as Industrial IoT, wearables, machine learning and more. It is built with an emphasis on broad chipset support, security, dependability, long-term support releases and a growing open source ecosystem...

The Zephyr community will be at the Zephyr Developer Summit, which takes place on June 27-30 in Prague, Czech Republic, and virtually as part of the first-ever Embedded Open Source Summit. [Register here for virtual attendance.]
Arduino will be joining Zephyr's Technical Steering Committee, along with Technology Innovation Institute and the American multinational semiconductor company Analog Devices (or ADI, who will also be joining its governing board). Arduino's CEO said "We believe that Zephyr OS is a truly special project that will play a significant role in the Arduino ecosystem and will be a big priority for us."

As a "Platinum"-level sponsor, ADI joins Antmicro, Baumer, Google, Intel, Meta, Nordic Semiconductor, NXP, Oticon, Qualcomm Innovation Center and T-Mobile.

An anonymous reader quotes a report from Ars Technica: Anyone who has taken a basic computer science class has undoubtedly spent time devising a sorting algorithm -- code that will take an unordered list of items and put them in ascending or descending order. It's an interesting challenge because there are so many ways of doing it and because people have spent a lot of time figuring out how to do this sorting as efficiently as possible. Sorting is so basic that algorithms are built into most standard libraries for programming languages. And, in the case of the C++ library used with the LLVM compiler, the code hasn't been touched in over a decade.

But Google's DeepMind AI group has now developed a reinforcement learning tool that can develop extremely optimized algorithms without first being trained on human code examples. The trick was to set it up to treat programming as a game. [...] The AlphaDev system developed x86 assembly algorithms that treated the latency of the code as a score and tried to minimize that score while ensuring that the code ran to completion without errors. Through reinforcement learning, AlphaDev gradually develops the ability to write tight, highly efficient code. [...]

Since AlphaDev did produce more efficient code, the team wanted to get these incorporated back into the LLVM standard C++ library. The problem here is that the code was in assembly rather than C++. So, they had to work backward and figure out the C++ code that would produce the same assembly. Once that was done, the code was incorporated into the LLVM toolchain -- the first time some of the code had been modified in over a decade. As a result, the researchers estimate that AlphaDev's code is now executed trillions of times a day. The research has been published in the journal Nature.

Microsoft's annual developer event Build 2023 unveiled ChatGPT's integration into Bing and an AI 'personal assistant' for Windows 11.

But Windows Central also notes two more big (non-AI) announcements: Windows 11 is getting cloud-powered OS backup and restore Smartphone owners have long enjoyed a similar functionality, where you could buy a new device and upon the first start, simply log in to your platform account and select "Restore my apps" from the cloud backup. And now Windows will be able to do the same. ["If the user chooses yes, Windows will automatically apply the old wallpaper and settings and even begin preloading apps you had installed on your old PC. Once the user hits the desktop, they'll see all their previously pinned apps already in the Taskbar, and clicking on them will initiate an automatic download from the Microsoft Store."]

Windows 11 on ARM devices gets a big boost [B]ecause Microsoft has no intention of dropping x86 support, they have been slow in adopting ARM architecture to make it a viable alternative for Windows users. With Build 2023, this is moving ahead...
Elsewhere Windows Central argues that "should result in a better experience on devices like the Surface Pro 9 (ARM), Surface Pro X, and the new Dell Inspiron 14 with a Snapdragon 8cx 2 processor.

On the gaming side of things, Unity with native Windows on ARM support will become available in early June. Once launched, the tool will let developers target Windows on ARM devices for current and future games, resulting in better performance. Unity is a very popular development platform for games, and native support for Windows on ARM is a welcome addition...

Visual Studio having Multi-platform App UI (MAUI) support for Arm will give developers another way to target Windows on ARM PCs.
Even Node.js v20.0.0 now officially supports ARM64 Windows, "allowing for native execution on the platform. The MSI, zip/7z packages, and executable are available from the Node.js download site along with all other platforms."

And in addition, Visual Studio 17.71 Preview 1 now ships with support for Linux development with C++.

Intel has proposed a potential simplification of the x86 architecture by creating a new x86S architecture that removes certain old features, such as 16-bit and some elements of 32-bit support. A technical note on Intel's developer blog proposes the change, with a 46-page white paper (PDF) providing more details. The Register reports: The result would be a family of processors which boot straight into x86-64 mode. That would mean bypassing the traditional series of transitions -- 16-bit real mode to 32-bit protected mode to 64-bit long mode; or 16-bit mode straight into 64-bit mode -- that chips are obliged to go through as the system starts up. [...] Some of the changes are quite dramatic, although the impact upon how most people use computers today would probably be invisible -- which is undoubtedly the idea.

Last week Linus Torvalds personally cleaned up the x86 memory copy code for Linux 6.4, Phoronix reports — and this week "he's merged more of his own code as he took issue with some of the code merged by Intel engineers as part of their Linear Address Masking enabling." Back during the Linux 6.2 days at the end of last year, Linus rejected the Intel LAM code at the time for various technical issues. Intel then reworked it for Linux 6.4. This time around Linus merged Intel LAM into Linux 6.4 as this new CPU feature for letting user-space store metadata within some bits of pointers without masking it out before use. Intel LAM — like Arm TBI — can be of use to virtual machines, profiling / sanitizers / tagging, and other applications. But this time around there were some less than ideal code that he personally took to sprucing up...

Torvalds reworked around one hundred lines of code for cleaning it up.
It's fun to read Torvalds' commit messages (included in both Phoronix articles). Torvalds begins by writing that the LAM updates "made me unhappy about how 'access_ok()' was done, and it actually turned out to have a couple of small bugs in it too..."

Phoronix shares some overlooked news from AMD's openSIL presentation at the OCP Regional Summit in April. Specifically, that AMD openSIL — their open-source x86 silicon initialization library — "is planned to eventually replace AMD's well known AGESA [BIOS utility]" around 2026, and "it will be supported across AMD's entire processor stack — just not limited to EPYC server processors as some were initially concerned..." Raj Kapoor, AMD Fellow and AMD's Chief Firmware Architect, in fact began the AMD openSIL presentation by talking about the challenges they've had with AGESA in adapting it to Coreboot for Chromebook purposes with Ryzen SoCs... With AMD openSIL not expected to be production ready until around 2026, this puts it roughly inline for an AMD Zen 6 or Zen 7 introduction. The proof of concept code for AMD Genoa is expected to come soon...

The presentation also noted that beyond AMD openSIL code being open-source, the openSIL specification will also be open. AMD "invites every silicon vendor" to participate in this open-source system firmware endeavor.

There's a major new update of QEMU, the open-source machine emulator, reports 9to5Linux: Coming a year after QEMU 7.0, the QEMU 8.0 release is here to improve support for ARM and RISC-V architectures.

- For ARM, it adds emulation support for FEAT_EVT, FEAT_FGT, and AArch32 ARMv8-R, CPU emulation for Cortex-A55 and Cortex-R52, support for a new Olimex STM32 H405 machine type, as well as gdbstub support for M-profile system registers.

- For the RISC-V architecture, QEMU 8.0 brings updated machine support for OpenTitan, PolarFire, and OpenSBI, additional ISA and Extension support for smstateen, native debug icount trigger, cache-related PMU events in virtual mode, Zawrs/Svadu/T-Head/Zicond extensions, and ACPI support. Moreover, RISC-V received multiple fixes covering PMP propagation for TLB, mret exceptions, uncompressed instructions, and other emulation/virtualization improvements.
Improvements were also made for the s390x (IBM Z) platform, the HP Precision Architecture (HPPA) platform, and x86.

Formerly known as LinuxBIOS, coreboot is defined by Wikipedia as "a software project aimed at replacing proprietary firmware (BIOS or UEFI) found in most computers with a lightweight firmware."

Phoronix is wondering if there's about to be a big announcement from AMD: AMD dropped a juicy tid-bit of information to be announced next month with "openSIL" [an open-source AMD x86 silicon initialization library], complete with AMD Coreboot support....

While about a decade ago AMD was big into Coreboot and at the time committed to it for future hardware platforms (2011: AMD To Support Coreboot On All Future CPUs) [and] open-source AGESA at the time did a lot of enabling around it, that work had died off. In more recent years, AMD's Coreboot contributions have largely been limited to select consumer APU/SoC platforms for Google Chromebook use. But issues around closing up the AGESA as well as concerns with the AMD Platform Security Processor (PSP) have diminished open-source firmware hopes in recent years....

For the Open Compute Project Regional Summit in Prague, there is a new entry added with a title of OSF on AMD — Enabled by openSIL (yes, folks, OSF as in "Open-Source Firmware").... [H]opefully this will prove to be a monumental shift for open-source firmware in the HPC server space.
From the talk's description: openSIL (AMD open-source x86 Silicon Initialization Library) offers the versatility, scalability, and light weight interface to allow for ease of integration with open-source and/or proprietary host boot solutions such as coreboot, UEFI and others and adds major flexibility to the overall platform design.

In other words, this library-based solution simply allows a platform integrator to scale from feature rich solutions such as UEFI to slim, lightweight, and secure solutions such as coreboot.
The description promises the talk will include demonstrations "highlighting system bring-up using openSIL integrated with coreboot and UEFI Host Firmware stacks on AMD's Genoa based platforms."

"IBM is the latest tech giant to unveil its own "AI supercomputer," this one composed of a bunch of virtual machines running within IBM Cloud," reports the Register: The system known as Vela, which the company claims has been online since May last year, is touted as IBM's first AI-optimized, cloud-native supercomputer, created with the aim of developing and training large-scale AI models. Before anyone rushes off to sign up for access, IBM stated that the platform is currently reserved for use by the IBM Research community. In fact, Vela has become the company's "go-to environment" for researchers creating advanced AI capabilities since May 2022, including work on foundation models, it said.

IBM states that it chose this architecture because it gives the company greater flexibility to scale up as required, and also the ability to deploy similar infrastructure into any IBM Cloud datacenter around the globe. But Vela is not running on any old standard IBM Cloud node hardware; each is a twin-socket system with 2nd Gen Xeon Scalable processors configured with 1.5TB of DRAM, and four 3.2TB NVMe flash drives, plus eight 80GB Nvidia A100 GPUs, the latter connected by NVLink and NVSwitch. This makes the Vela infrastructure closer to that of a high performance compute site than typical cloud infrastructure, despite IBM's insistence that it was taking a different path as "traditional supercomputers weren't designed for AI."

It is also notable that IBM chose to use x86 processors rather than its own Power 10 chips, especially as these were touted by Big Blue as being ideally suited for memory-intensive workloads such as large-model AI inferencing.
Thanks to Slashdot reader guest reader for sharing the story.

According to a new report by Dean McCarron of Mercury Research, the x86 processor market has just endured "the largest on-quarter and on-year declines in our 30-year history." "Based on previously published third-party data, McCarron is also reasonably sure that the 2022 Q4 and full-year numbers represent the worst downturn in PC processor history," adds Tom's Hardware. From the report: The x86 processor downturn observed has been precipitated by the terrible twosome of lower demand and an inventory correction. This menacing pincer movement has resulted in 2022 unit shipments of 374 million processors (excluding ARM), a figure 21% lower than in 2021. Revenues were $65 billion, down 19 percent YoY. McCarron was keen to emphasize that Mercury's gloomy stats about x86 shipments through 2022 do not necessarily directly correlate with x86 PC (processors) shipments to end users. Earlier, we mentioned that the two downward driving forces were inventory adjustments and a slowing of sales -- but which played the most significant part in this x86 record slump?

The Mercury Research analyst explained, "Most of the downturn in shipments is blamed on excess inventory shipping in prior quarters impacting current sales." A perfect storm is thus brewing as "CPU suppliers are also deliberately limiting shipments to help increase the rate of inventory consumption... [and] PC demand for processors is lower, and weakening macroeconomic concerns are driving PC OEMs to reduce their inventory as well." Mercury also asserted that the trend is likely to continue through H1 2023. Its thoughts about the underlying inventory shenanigans should also be evidenced by upcoming financials from the major players in the next few months. [...]

McCarron shines a glimmer of light in the wake of this gloom, reminding us that overall processor revenue was still higher in 2022 than any year before the 2020s began. Another ray of light shone on AMD, with its gains in server CPU share, one of the only segments which saw some growth in Q4 2022. Also, AMD gained market share in the shrinking desktop and laptop markets.

An anonymous reader quotes a report from VentureBeat: Red Hat is perhaps best known as a Linux operating system vendor, but it is the company's OpenShift platform that represents its fastest growing segment. Today, Red Hat announced the general availability of OpenShift 4.12, bringing a series of new capabilities to the company's hybrid cloud application delivery platform. OpenShift is based on the open source Kubernetes container orchestration system, originally developed by Google, that has been run as the flagship project of the Linux Foundation's Cloud Native Computing Foundation (CNCF) since 2014. [...] With the new release, Red Hat is integrating new capabilities to help improve security and compliance for OpenShift, as well as new deployment options on ARM-based architectures. The OpenShift 4.12 release comes as Red Hat continues to expand its footprint, announcing partnerships with Oracle and SAP this week.

The financial importance of OpenShift to Red Hat and its parent company IBM has also been revealed, with IBM reporting in its earnings that OpenShift is a $1 billion business. "Open-source solutions solve major business problems every day, and OpenShift is just another example of how Red Hat brings business and open source together for the benefit of all involved," Mike Barrett, VP of product management at Red Hat, told VentureBeat. "We're very proud of what we have accomplished thus far, but we're not resting at $1B." [...]

OpenShift, like many applications developed in the last several decades, originally was built just for the x86 architecture that runs on CPUs from Intel and AMD. That situation is increasingly changing as OpenShift is gaining more support to run on the ARM processor with the OpenShift 4.12 update. Barrett noted that Red Hat OpenShift announced support for the AWS Graviton ARM architecture in 2022. He added that OpenShift 4.12 expands that offering to Microsoft Azure ARM instances. "We find customers with a significant core consumption rate for a singular computational deliverable are gravitating toward ARM first," Barrett said.

Overall, Red Hat is looking to expand the footprint of where its technologies are able to run, which also new cloud providers. On Jan. 31, Red Hat announced that for the first time, Red Hat Enterprise Linux (RHEL) would be available as a supported platform on Oracle Cloud Infrastructure (OCI). While RHEL is now coming to OCI, OpenShift isn't -- at least not yet. "Right now, it's just RHEL available on OCI," Mike Evans, vice president, technical business development at Red Hat, told VentureBeat. "We're evaluating what other Red Hat technologies, including OpenShift, may come to Oracle Cloud Infrastructure but this will ultimately be driven by what our joint customers want."

An anonymous reader shares this report from OMG! Ubuntu: Developers have just uncorked a brand new release of Wine, the open source compatibility layer that allows Windows apps to run on Linux.

A substantial update, Wine 8.0 is fermented from a year's worth of active development (roughly 8,600 changes in total). From that, a wealth of improvements are provided across every part of the Wine experience, from app compatibility, through to performance, and a nicer looking UI....

Notable highlights in Wine 8.0 include the completion of PE conversion, meaning all modules can be built in PE format. Wine devs say this work is an important milestone towards supporting "copy protection, 32-bit applications on 64-bit hosts, Windows debuggers, x86 applications on ARM", and more.

Initially mentioned during their Innovation 2022 opening keynote by Intel CEO Pat Gelsinger, Intel has unveiled its highly anticipated 6 GHz out-of-the-box processor, the Core i9-13900KS. The Core i9-13900KS has 24-cores (8P+16E) within its hybrid architecture design of performance and efficiency cores, with the exact fundamental specifications of the Core i9-13900K, but with an impressive P-core turbo of up to 6 GHz. From a report: Based on Intel's Raptor Lake-S desktop series, Intel claims that the Core i9-13900KS is the first desktop processor to reach 6 GHz out of the box without overclocking. Available from today, the Core i9-13900KS has a slightly higher base TDP of 150 W (versus 125 on the 13900K), 36 MB of Intel's L3 smart cache, and is pre-binned through a unique selection process to ensure the Core i9-13900KS's special edition status for their highest level of frequency of 6 GHz in a desktop chip out of the box, without the need to overclock manually.

The Core i9-13900KS has been a long-awaited entrant to Intel's Raptor Lake-S for desktop series, with previous reports from Intel during their Innovation 2022 keynote that a 6 GHz out-of-the-box processor was on the horizon for this year. As Intel highlights, the Core i9-13900KS represents a significant milestone for desktop PCs, with its 6 GHz out-of-the-box P-Core turbo frequency. This makes it one of the fastest desktop x86 processors, at least from the perspective that users don't need to overclock anything to attain these ridiculous core frequencies. From Intel's sneak peek video on YouTube published on Jan 10th, the Core i9-13900KS looks to have reached 6 GHz on two of the eight performance (P) cores, with a clock speed of up to 5.6 GHz on the remaining six cores, which is very impressive.

One of the adjustments Intel needed to make to power limitations to achieve these frequencies is somewhat hazy. Intel hasn't specified if the Core i9-13900KS is a special binned part, but from previous KS launches, this has been the case, and it's expected that it is still the case. The reports of Core i9-13900K chips being overclocked to 6 GHz at ambient are few and far between, with only the best examples and those with very aggressive and premium ambient cooling solutions capable of this. [...] The Intel Core i9-13900KS is available to buy now at most retailers, with an MSRP of $699. This is $40 cheaper than the previous Core i9-12900KS ($739) that launched last year. Based on current MSRP pricing, the Core i9-13900KS is $110 more than the current Core i9-13900K.

An anonymous reader quotes a report from Ars Technica: Google's keynote at the RISC-V Summit was all about bold proclamations [...]. Lars Bergstrom, Android's director of engineering, wants RISC-V to be seen as a "tier-1 platform" in Android, which would put it on par with Arm. That's a big change from just six months ago. Bergstrom says getting optimized Android builds on RISC-V will take "a lot of work" and outlined a roadmap that will take "a few years" to come to fruition, but AOSP started to land official RISC-V patches back in September. The build system is up and running, and anyone can grab the latest "riscv64" branch whenever they want -- and yes, in line with its recent Arm work, Google wants RISC-V on Android to be 64-bit only. For now, the most you can get is a command line, and Bergstrom's slide promised "initial emulator support by the start of 2023, with Android RunTime (ART) support for Java workloads following during Q1."

One of Bergstrom's slides featured the above "to-do" list, which included a ton of major Android components. Unlike Android's unpolished support for x86, Bergstrom promised a real push for quality with RISC-V, saying, "We need to do all of the work to move from a prototype and something that runs to something that's really singing -- that's showing off the best-in-class processors that [RISC-V International Chairman Krste Asanovic] was mentioning in the previous talk." Once Google does get Android up and running on RISC-V, then it will be up to manufacturers and the app ecosystem to back the platform. What's fun about the Android RunTime is that when ART supports RISC-V, a big chunk of the Android app ecosystem will come with it. Android apps ship as Java code, and the way that becomes an ARM app is when the Android Runtime compiles it into ARM code. Instead, it will soon compile into RISC-V code with no extra work from the developer. Native code that isn't written in Java, like games and component libraries, will need to be ported over, but starting with Java code is a big jump-start.

In her opening remarks, RISC-V International (the nonprofit company that owns the architecture) CEO Calista Redmond argued that "RISC-V is inevitable" thanks to the open business model and wave of open chip design that it can create, and it's getting hard to argue against that. While the show was mostly about the advantages of RISC-V, I want to add that the biggest reason RISC-V seems inevitable is that current CPU front-runner Arm has become an unstable, volatile company, and it feels like any viable alternative would have a good shot at success right now. [...] The other reason to kick Arm to the curb is the US-China trade war, specifically that Chinese companies (and the Chinese government) would really like to distance themselves from Western technology. [...] RISC-V is seen as a way to be less reliant on the West. While the project started at UC Berkeley, RISC-V International says the open source architecture is not subject to US export law. In 2019, the RISC-V Foundation actually moved from the US to Switzerland and became "RISC-V International," all to try to avoid picking a side in the US-China trade war. The result is that Chinese tech companies are rallying around RISC-V as the future chip architecture. One Chinese company hit by US export restrictions, the e-commerce giant Alibaba, has been the leading force in bringing RISC-V support to Android, and with Chinese companies playing a huge part in the Android ecosystem, it makes sense that Google would throw open the doors for official support. Now we just need someone to build a phone.