Futureweb

Software

The KVM PML pull is for 7.4

A KVM maintainer's October 16 pull for Linux 7.4 includes AMD page-modification logging. A maintainer reply says the pulls were taken. That merge is not a 7.4 tarball.

The short version

No. Sean Christopherson sent the x86 misc pull on October 16, and a reply says it was pulled. Phoronix reported the merge on October 27. A pull is not the 7.4 release.

The pull

On October 16, 2026, Sean Christopherson sent a git pull for KVM x86 misc changes aimed at Linux 7.4. The message says the branch includes support for page-modification logging on SVM, which is AMD's hardware dirty-page tracking for guests. The same message lists a long set of other KVM fixes. This page is about the PML line and the fact of the pull. It will not walk through the other fixes, and it will not describe how a guest page is logged. A later reply on the list says the pulls were taken. Phoronix reported the merge on October 27.

A pull is not a tarball

The EFI-variable brief made this distinction for a different pull: mail that a maintainer has merged is not the kernel tarball a distribution will ship as 7.4. The same line applies here. Linux 7.4 has not been cut by this pull request. The short-slice brief was an earlier 7.4 item about a scheduler change. The sound pull named an audio flood. Memblock search was filed as something other than a release. PML is one more 7.4 KVM item, and it waits on the same future tarball.The EFI pull.

What PML means in the pull

The pull's own summary line is the definition this page will use: support for page-modification logging on SVM, so a hypervisor can see which guest pages changed. Phoronix ties that support to AMD EPYC Zen 6. The pull does not, in the summary read here, announce a ship date for Zen 6 hardware. Dirty-page tracking is a virtualization feature. It is not a security advisory, and this page will not turn the pull message into a configuration guide. Asked directly, How is this different from the EFI stub brief? The EFI brief was a different pull about a variable and a tarball. This one is KVM dirty-page logging on AMD SVM.The short slice.

The s390 sentence

Phoronix's October 27 story also says Linux 7.4 KVM includes initial support for ARM64 guests on IBM s390, following an IBM and Arm collaboration announced earlier in the year. This page did not open that pull. The sentence stays Phoronix's until the s390 series is the document in front of a later brief. The x86 misc pull is the document today, and PML is the line in it that the wire led with. Asked directly, Did this page open a separate s390 pull? No. The ARM64-on-s390 line is Phoronix's sentence. The primary opened here is the x86 misc pull.The sound pull.

What the pull also contains

The misc pull's cover letter lists many other changes, including checks around nested state and a note about not leaking stack contents in a synthetic message path. Those lines are maintainer bugfixes inside a merge request. This page will not restate them as instructions, and it will not rank them. A reader who wants the full list has the pull message. The memory-safety brief is the standing note on how this desk talks about safety language in a release. A pull cover is not yet that release.Memory safety in the notes.

The JetBrains terminal is a different library

Today's JetBrains brief is an IDE swapping a terminal parser. This brief is a kernel maintainer landing guest dirty-page logging. Both are software filings because the day needed the documents it actually had. They do not share a component. The Node patch was a runtime release. KVM here is pre-release mail. The short answer this page will stand on is this: No. Sean Christopherson sent the x86 misc pull on October 16, and a reply says it was pulled. Phoronix reported the merge on October 27. A pull is not the 7.4 release.The JetBrains terminal.

Who it is for

The people in scope are operators who run KVM on AMD SVM hardware once a 7.4 kernel that contains this pull actually ships, and the distributions that package that kernel. Nobody has that tarball from this mail. Phoronix's readers are the audience of the October 27 account. The pull's readers are the kernel list. Asked directly, What did the maintainer reply say? The reply says the pulls were taken. That is a merge into the KVM queue, not a release announcement.

Memblock was the earlier warning

Memblock search was filed because a search result looked like a release and was not one. The KVM pull is easier to misread the same way: a news headline says merged for 7.4, and a reader hears that 7.4 is out. The merge reply says the pulls were taken into the KVM queue. The version number 7.4 is the target. The tarball is still ahead. Asked directly, What does Phoronix add on October 27? Phoronix reports KVM changes merged for Linux 7.4, including AMD PML for Zen 6 and an initial ARM64-on-s390 line.Memblock search.

The record

The record is the October 16 misc pull, the reply that says the pulls were taken, and Phoronix's October 27 account. PML on SVM is in the pull. The ARM64-on-s390 line is in the news story, not in the pull this page opened. Linux 7.4 as a release tarball is not this document. The networking merge coverage for 7.4 is a separate filing on the same series. Asked directly, Who sent the KVM x86 misc pull for 7.4? Sean Christopherson, on October 16, 2026. The message lists page-modification logging on SVM among the changes.Linux 7.4 networking.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. KVM x86 misc pull
  2. Phoronix
  3. Pull reply

Questions

Who sent the KVM x86 misc pull for 7.4?

Sean Christopherson, on October 16, 2026. The message lists page-modification logging on SVM among the changes.

What did the maintainer reply say?

The reply says the pulls were taken. That is a merge into the KVM queue, not a release announcement.

What does Phoronix add on October 27?

Phoronix reports KVM changes merged for Linux 7.4, including AMD PML for Zen 6 and an initial ARM64-on-s390 line.

Did this page open a separate s390 pull?

No. The ARM64-on-s390 line is Phoronix's sentence. The primary opened here is the x86 misc pull.

How is this different from the EFI stub brief?

The EFI brief was a different pull about a variable and a tarball. This one is KVM dirty-page logging on AMD SVM.