qapi: convert to explicit intro section syntax
cover qapi: convert to explicit intro section syntax
GitLab CI: https://gitlab.com/jsnow/qemu/-/pipelines/2638342206
Hi, this patchset converts some of the most trivial modules to use the new explicit intro syntax. This particular patchset does not differentiate between "trivial" conversions and those that take slightly more liberty in refactoring, but there are (debatably?) no such cases in this patchset.
John Snow (14):
qapi: convert intro sections for error.json
qapi: convert intro sections for acpi-hest.json
qapi: convert intro sections for ebpf.json
qapi: convert intro sections for uefi.json
qapi: convert intro sections for compat.json
qapi: convert intro sections for vfio.json
qapi: convert intro sections for trace.json
qapi: convert intro sections for misc-arm.json
qapi: convert intro sections for cryptodev.json
qapi: convert intro sections for machine-common.json
qapi: convert intro sections for accelerator.json
qapi: convert intro sections for authz.json
qapi: convert intro sections for yank.json
qapi: convert intro sections for replay.json
qapi/accelerator.json | 18 ++++++---------- qapi/acpi-hest.json | 4 ++-- qapi/authz.json | 21 +++++++------------ qapi/compat.json | 9 +++----- qapi/cryptodev.json | 18 ++++++---------- qapi/ebpf.json | 14 ++++++------- qapi/error.json | 3 +-- qapi/machine-common.json | 19 +++++++---------- qapi/misc-arm.json | 24 +++++++++------------ qapi/replay.json | 45 ++++++++++++++++++---------------------- qapi/trace.json | 12 ++++------- qapi/uefi.json | 5 ++--- qapi/vfio.json | 19 ++++++++--------- qapi/yank.json | 28 ++++++++++--------------- 14 files changed, 94 insertions(+), 145 deletions(-)
Signature · 1 line
2.54.0
PATCH 1/14 qapi: convert intro sections for error.json
--- qapi/error.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
qapi/error.json +1 -2
@@ -9,8 +9,7 @@ ## # @QapiErrorClass: -# -# QEMU error classes +# QEMU error classes # # @GenericError: this is used for errors that don't require a specific # error class. This should be the default case for most errors
Signature · 1 line
2.54.0
PATCH 2/14 qapi: convert intro sections for acpi-hest.json
In reply to John Snow--- qapi/acpi-hest.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
qapi/acpi-hest.json +2 -2
@@ -13,8 +13,8 @@ ## # @inject-ghes-v2-error: -# -# Inject an error with additional ACPI 6.1 GHESv2 error information +# Inject an error with additional ACPI 6.1 GHESv2 error +# information # # @cper: contains a base64 encoded string with raw data for a single # CPER record with Generic Error Status Block, Generic Error Data
Signature · 1 line
2.54.0
PATCH 3/14 qapi: convert intro sections for ebpf.json
In reply to John Snow--- qapi/ebpf.json | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-)
qapi/ebpf.json +6 -8
@@ -20,8 +20,7 @@ ## # @EbpfObject: -# -# An eBPF ELF object. +# An eBPF ELF object. # # @object: the eBPF object encoded in base64 #
@@ -33,8 +32,7 @@ ## # @EbpfProgramID: -# -# The eBPF programs that can be gotten with `request-ebpf`. +# The eBPF programs that can be gotten with `request-ebpf`. # # @rss: Receive side scaling, technology that allows steering traffic # between queues by calculation hash. Users may set up
@@ -49,10 +47,10 @@ ## # @request-ebpf: -# -# Retrieve an eBPF object that can be loaded with libbpf. Management -# applications (e.g. libvirt) may load it and pass file descriptors to -# QEMU, so they can run running QEMU without BPF capabilities. +# Retrieve an eBPF object that can be loaded with libbpf. +# Management applications (e.g. libvirt) may load it and pass file +# descriptors to QEMU, so they can run running QEMU without BPF +# capabilities. # # @id: The ID of the program to return. #
Signature · 1 line
2.54.0
PATCH 4/14 qapi: convert intro sections for uefi.json
In reply to John Snow--- qapi/uefi.json | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
qapi/uefi.json +2 -3
@@ -17,9 +17,8 @@ ## # @UefiVariable: -# -# UEFI Variable. Check the UEFI specification for more detailed -# information on the fields. +# UEFI Variable. Check the UEFI specification for more detailed +# information on the fields. # # @guid: variable namespace GUID #
Signature · 1 line
2.54.0
PATCH 5/14 qapi: convert intro sections for compat.json
In reply to John Snow--- qapi/compat.json | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-)
qapi/compat.json +3 -6
@@ -9,8 +9,7 @@ ## # @CompatPolicyInput: -# -# Policy for handling "funny" input. +# Policy for handling "funny" input. # # @accept: Accept silently #
@@ -25,8 +24,7 @@ ## # @CompatPolicyOutput: -# -# Policy for handling "funny" output. +# Policy for handling "funny" output. # # @accept: Pass on unchanged #
@@ -39,8 +37,7 @@ ## # @CompatPolicy: -# -# Policy for handling deprecated management interfaces. +# Policy for handling deprecated management interfaces. # # This is intended for testing users of the management interfaces. #
Signature · 1 line
2.54.0
PATCH 6/14 qapi: convert intro sections for vfio.json
In reply to John Snow--- qapi/vfio.json | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-)
qapi/vfio.json +9 -10
@@ -10,14 +10,13 @@ ## # @QapiVfioMigrationState: -# -# An enumeration of the VFIO device migration states. In addition to -# the regular states, there are prepare states (with 'prepare' suffix) -# which indicate that the device is just about to transition to the -# corresponding state. Note that seeing a prepare state for state X -# doesn't guarantee that the next state will be X, as the state -# transition can fail and the device may transition to a different -# state instead. +# An enumeration of the VFIO device migration states. In addition +# to the regular states, there are prepare states (with 'prepare' +# suffix) which indicate that the device is just about to +# transition to the corresponding state. Note that seeing a +# prepare state for state X doesn't guarantee that the next state +# will be X, as the state transition can fail and the device may +# transition to a different state instead. # # @stop: The device is stopped. #
@@ -49,8 +48,8 @@ ## # @VFIO_MIGRATION: -# -# This event is emitted when a VFIO device migration state is changed. +# This event is emitted when a VFIO device migration state is +# changed. # # @device-id: The device's id, if it has one. #
Signature · 1 line
2.54.0
PATCH 7/14 qapi: convert intro sections for trace.json
In reply to John Snow--- qapi/trace.json | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-)
qapi/trace.json +4 -8
@@ -14,8 +14,7 @@ ## # @TraceEventState: -# -# State of a tracing event. +# State of a tracing event. # # @unavailable: The event is statically disabled. #
@@ -30,8 +29,7 @@ ## # @TraceEventInfo: -# -# Information of a tracing event. +# Information of a tracing event. # # @name: Event name. #
@@ -44,8 +42,7 @@ ## # @trace-event-get-state: -# -# Query the state of events. +# Query the state of events. # # @name: Event name pattern (case-sensitive glob). #
@@ -65,8 +62,7 @@ ## # @trace-event-set-state: -# -# Set the dynamic tracing state of events. +# Set the dynamic tracing state of events. # # @name: Event name pattern (case-sensitive glob). #
Signature · 1 line
2.54.0
PATCH 8/14 qapi: convert intro sections for misc-arm.json
In reply to John Snow--- qapi/misc-arm.json | 24 ++++++++++-------------- 1 file changed, 10 insertions(+), 14 deletions(-)
qapi/misc-arm.json +10 -14
@@ -5,11 +5,10 @@ ## # @GICCapability: -# -# The struct describes capability for a specific GIC (Generic -# Interrupt Controller) version. These bits are not only decided by -# QEMU/KVM software version, but also decided by the hardware that the -# program is running upon. +# The struct describes capability for a specific GIC (Generic +# Interrupt Controller) version. These bits are not only decided +# by QEMU/KVM software version, but also decided by the hardware +# that the program is running upon. # # @version: version of GIC to be described. Currently, only 2 and 3 # are supported.
@@ -29,12 +28,11 @@ ## # @query-gic-capabilities: +# It will return a list of `GICCapability` objects that describe +# its capability bits. # -# It will return a list of `GICCapability` objects that describe its -# capability bits. -# -# On non-ARM targets this command will report an error as the GIC -# technology is not applicable. +# On non-ARM targets this command will report an error as the GIC +# technology is not applicable. # # Since: 2.6 #
@@ -48,8 +46,7 @@ ## # @SsidSizeMode: -# -# SMMUv3 SubstreamID size configuration mode. +# SMMUv3 SubstreamID size configuration mode. # # @auto: derive from host IOMMU capabilities #
@@ -64,8 +61,7 @@ ## # @OasMode: -# -# SMMUv3 Output Address Size configuration mode. +# SMMUv3 Output Address Size configuration mode. # # @auto: derive from host IOMMU capabilities #
Signature · 1 line
2.54.0
PATCH 9/14 qapi: convert intro sections for cryptodev.json
In reply to John Snow--- qapi/cryptodev.json | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-)
qapi/cryptodev.json +6 -12
@@ -12,8 +12,7 @@ ## # @QCryptodevBackendAlgoType: -# -# The supported algorithm types of a crypto device. +# The supported algorithm types of a crypto device. # # @sym: symmetric encryption #
@@ -26,8 +25,7 @@ ## # @QCryptodevBackendServiceType: -# -# The supported service types of a crypto device. +# The supported service types of a crypto device. # # @cipher: Symmetric Key Cipher service #
@@ -46,8 +44,7 @@ ## # @QCryptodevBackendType: -# -# The crypto device backend type +# The crypto device backend type # # @builtin: the QEMU builtin support #
@@ -62,8 +59,7 @@ ## # @QCryptodevBackendClient: -# -# Information about a queue of crypto device. +# Information about a queue of crypto device. # # @queue: the queue index of the crypto device #
@@ -77,8 +73,7 @@ ## # @QCryptodevInfo: -# -# Information about a crypto device. +# Information about a crypto device. # # @id: the id of the crypto device #
@@ -95,8 +90,7 @@ ## # @query-cryptodev: -# -# Return information about current crypto devices. +# Return information about current crypto devices. # # Since: 8.0 ##
Signature · 1 line
2.54.0
PATCH 10/14 qapi: convert intro sections for machine-common.json
In reply to John Snow--- qapi/machine-common.json | 19 +++++++------------ 1 file changed, 7 insertions(+), 12 deletions(-)
qapi/machine-common.json +7 -12
@@ -12,9 +12,8 @@ ## # @S390CpuEntitlement: -# -# An enumeration of CPU entitlements that can be assumed by a virtual -# S390 CPU +# An enumeration of CPU entitlements that can be assumed by a +# virtual S390 CPU # # Since: 8.2 ##
@@ -23,8 +22,7 @@ ## # @CpuTopologyLevel: -# -# An enumeration of CPU topology levels. +# An enumeration of CPU topology levels. # # @thread: thread level, which would also be called SMT level or # logical processor level. The @threads option in
@@ -65,9 +63,8 @@ ## # @CacheLevelAndType: -# -# Caches a system may have. The enumeration value here is the -# combination of cache level and cache type. +# Caches a system may have. The enumeration value here is the +# combination of cache level and cache type. # # @l1d: L1 data cache. #
@@ -84,8 +81,7 @@ ## # @SmpCacheProperties: -# -# Cache information for SMP system. +# Cache information for SMP system. # # @cache: Cache name, which is the combination of cache level and # cache type.
@@ -103,8 +99,7 @@ ## # @SmpCachePropertiesWrapper: -# -# List wrapper of `SmpCacheProperties`. +# List wrapper of `SmpCacheProperties`. # # @caches: the list of `SmpCacheProperties`. #
Signature · 1 line
2.54.0
PATCH 11/14 qapi: convert intro sections for accelerator.json
In reply to John Snow--- qapi/accelerator.json | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-)
qapi/accelerator.json +6 -12
@@ -13,8 +13,7 @@ ## # @KvmInfo: -# -# Information about support for KVM acceleration +# Information about support for KVM acceleration # # @enabled: true if KVM acceleration is active #
@@ -26,8 +25,7 @@ ## # @query-kvm: -# -# Return information about KVM acceleration +# Return information about KVM acceleration # # Features: #
@@ -46,8 +44,7 @@ ## # @x-accel-stats: -# -# Query accelerator statistics +# Query accelerator statistics # # Features: #
@@ -63,8 +60,7 @@ ## # @Accelerator: -# -# Information about support for MSHV acceleration +# Information about support for MSHV acceleration # # @hvf: Apple Hypervisor.framework #
@@ -88,8 +84,7 @@ ## # @AcceleratorInfo: -# -# Information about support for various accelerators +# Information about support for various accelerators # # @enabled: the accelerator that is in use #
@@ -102,8 +97,7 @@ ## # @query-accelerators: -# -# Return information about accelerators +# Return information about accelerators # # Returns: @AcceleratorInfo #
Signature · 1 line
2.54.0
PATCH 12/14 qapi: convert intro sections for authz.json
In reply to John Snow--- qapi/authz.json | 21 +++++++-------------- 1 file changed, 7 insertions(+), 14 deletions(-)
qapi/authz.json +7 -14
@@ -9,8 +9,7 @@ ## # @QAuthZListPolicy: -# -# The authorization policy result +# The authorization policy result # # @deny: deny access #
@@ -24,8 +23,7 @@ ## # @QAuthZListFormat: -# -# The authorization policy match format +# The authorization policy match format # # @exact: an exact string match #
@@ -39,8 +37,7 @@ ## # @QAuthZListRule: -# -# A single authorization rule. +# A single authorization rule. # # @match: a string or glob to match against a user identity #
@@ -57,8 +54,7 @@ ## # @AuthZListProperties: -# -# Properties for authz-list objects. +# Properties for authz-list objects. # # @policy: Default policy to apply when no rule matches (default: # deny)
@@ -73,8 +69,7 @@ ## # @AuthZListFileProperties: -# -# Properties for authz-listfile objects. +# Properties for authz-listfile objects. # # @filename: File name to load the configuration from. The file must # contain valid JSON for `AuthZListProperties`.
@@ -93,8 +88,7 @@ ## # @AuthZPAMProperties: -# -# Properties for authz-pam objects. +# Properties for authz-pam objects. # # @service: PAM service name to use for authorization #
@@ -105,8 +99,7 @@ ## # @AuthZSimpleProperties: -# -# Properties for authz-simple objects. +# Properties for authz-simple objects. # # @identity: Identifies the allowed user. Its format depends on the # network service that authorization object is associated with.
Signature · 1 line
2.54.0
PATCH 13/14 qapi: convert intro sections for yank.json
In reply to John Snow--- qapi/yank.json | 28 +++++++++++----------------- 1 file changed, 11 insertions(+), 17 deletions(-)
qapi/yank.json +11 -17
@@ -10,9 +10,8 @@ ## # @YankInstanceType: -# -# An enumeration of yank instance types. See `YankInstance` for more -# information. +# An enumeration of yank instance types. See `YankInstance` for +# more information. # # Since: 6.0 ##
@@ -21,9 +20,8 @@ ## # @YankInstanceBlockNode: -# -# Specifies which block graph node to yank. See `YankInstance` for -# more information. +# Specifies which block graph node to yank. See `YankInstance` +# for more information. # # @node-name: the name of the block graph node #
@@ -34,9 +32,8 @@ ## # @YankInstanceChardev: -# -# Specifies which character device to yank. See `YankInstance` for -# more information. +# Specifies which character device to yank. See `YankInstance` +# for more information. # # @id: the chardev's ID #
@@ -47,9 +44,8 @@ ## # @YankInstance: -# -# A yank instance can be yanked with the `yank` qmp command to recover -# from a hanging QEMU. +# A yank instance can be yanked with the `yank` qmp command to +# recover from a hanging QEMU. # # @type: yank instance type #
@@ -74,9 +70,8 @@ ## # @yank: -# -# Try to recover from hanging QEMU by yanking the specified instances. -# See `YankInstance` for more information. +# Try to recover from hanging QEMU by yanking the specified +# instances. See `YankInstance` for more information. # # @instances: the instances to be yanked #
@@ -101,8 +96,7 @@ ## # @query-yank: -# -# Query yank instances. See `YankInstance` for more information. +# Query yank instances. See `YankInstance` for more information. # # TODO: This line is a hack to separate the example from the body #
Signature · 1 line
2.54.0
Re: [PATCH 13/14] qapi: convert intro sections for yank.json
Quoted 1 line · On Mon, 29 Jun 2026 17:36:23 -0400 John Snow <[email protected]> wrote:
Signed-off-by John Snow <[email protected]>
Quoted 78 lines
--- qapi/yank.json | 28 +++++++++++----------------- 1 file changed, 11 insertions(+), 17 deletions(-)qapi/yank.json +11
-17@@ -10,9 +10,8 @@ ## # @YankInstanceType: -# -# An enumeration of yank instance types. See `YankInstance` for more -# information. +# An enumeration of yank instance types. See `YankInstance` for +# more information. # # Since: 6.0 ##@@ -21,9 +20,8 @@ ## # @YankInstanceBlockNode: -# -# Specifies which block graph node to yank. See `YankInstance` for -# more information. +# Specifies which block graph node to yank. See `YankInstance` +# for more information. # # @node-name: the name of the block graph node #@@ -34,9 +32,8 @@ ## # @YankInstanceChardev: -# -# Specifies which character device to yank. See `YankInstance` for -# more information. +# Specifies which character device to yank. See `YankInstance` +# for more information. # # @id: the chardev's ID #@@ -47,9 +44,8 @@ ## # @YankInstance: -# -# A yank instance can be yanked with the `yank` qmp command to recover -# from a hanging QEMU. +# A yank instance can be yanked with the `yank` qmp command to +# recover from a hanging QEMU. # # @type: yank instance type #@@ -74,9 +70,8 @@ ## # @yank: -# -# Try to recover from hanging QEMU by yanking the specified instances. -# See `YankInstance` for more information. +# Try to recover from hanging QEMU by yanking the specified +# instances. See `YankInstance` for more information. # # @instances: the instances to be yanked #@@ -101,8 +96,7 @@ ## # @query-yank: -# -# Query yank instances. See `YankInstance` for more information. +# Query yank instances. See `YankInstance` for more information. # # TODO: This line is a hack to separate the example from the body #
PATCH 14/14 qapi: convert intro sections for replay.json
In reply to John Snow--- qapi/replay.json | 45 ++++++++++++++++++++------------------------- 1 file changed, 20 insertions(+), 25 deletions(-)
qapi/replay.json +20 -25
@@ -12,8 +12,7 @@ ## # @ReplayMode: -# -# Mode of the replay subsystem. +# Mode of the replay subsystem. # # @none: normal execution mode. Replay or record are not enabled. #
@@ -30,8 +29,7 @@ ## # @ReplayInfo: -# -# Record/replay information. +# Record/replay information. # # @mode: current mode. #
@@ -47,10 +45,9 @@ ## # @query-replay: -# -# Retrieve the record/replay information. It includes current -# instruction count which may be used for `replay-break` and -# `replay-seek` commands. +# Retrieve the record/replay information. It includes current +# instruction count which may be used for `replay-break` and +# `replay-seek` commands. # # Returns: record/replay information. #
@@ -66,13 +63,13 @@ ## # @replay-break: -# -# Set replay breakpoint at instruction count @icount. Execution stops -# when the specified instruction is reached. There can be at most one -# breakpoint. When breakpoint is set, any prior one is removed. The -# breakpoint may be set only in replay mode and only "in the future", -# i.e. at instruction counts greater than the current one. The -# current instruction count can be observed with `query-replay`. +# Set replay breakpoint at instruction count @icount. Execution +# stops when the specified instruction is reached. There can be +# at most one breakpoint. When breakpoint is set, any prior one +# is removed. The breakpoint may be set only in replay mode and +# only "in the future", i.e. at instruction counts greater than +# the current one. The current instruction count can be observed +# with `query-replay`. # # @icount: instruction count to stop at #
@@ -87,9 +84,8 @@ ## # @replay-delete-break: -# -# Remove replay breakpoint which was set with `replay-break`. The -# command is ignored when there are no replay breakpoints. +# Remove replay breakpoint which was set with `replay-break`. The +# command is ignored when there are no replay breakpoints. # # Since: 5.2 #
@@ -102,13 +98,12 @@ ## # @replay-seek: -# -# Automatically proceed to the instruction count @icount, when -# replaying the execution. The command automatically loads nearest -# snapshot and replays the execution to find the desired instruction. -# When there is no preceding snapshot or the execution is not -# replayed, then the command fails. Instruction count can be obtained -# with the `query-replay` command. +# Automatically proceed to the instruction count @icount, when +# replaying the execution. The command automatically loads +# nearest snapshot and replays the execution to find the desired +# instruction. When there is no preceding snapshot or the +# execution is not replayed, then the command fails. Instruction +# count can be obtained with the `query-replay` command. # # @icount: target instruction count #
Signature · 1 line
2.54.0
Borislav Petkov
maintainerQuoted 24 lines · John Snow
GitLab CI: https://gitlab.com/jsnow/qemu/-/pipelines/2638342206
Hi, this patchset converts some of the most trivial modules to use the new explicit intro syntax. This particular patchset does not differentiate between "trivial" conversions and those that take slightly more liberty in refactoring, but there are (debatably?) no such cases in this patchset.
John Snow (14):
qapi: convert intro sections for error.json
qapi: convert intro sections for acpi-hest.json
qapi: convert intro sections for ebpf.json
qapi: convert intro sections for uefi.json
qapi: convert intro sections for compat.json
qapi: convert intro sections for vfio.json
qapi: convert intro sections for trace.json
qapi: convert intro sections for misc-arm.json
qapi: convert intro sections for cryptodev.json
qapi: convert intro sections for machine-common.json
qapi: convert intro sections for accelerator.json
qapi: convert intro sections for authz.json
qapi: convert intro sections for yank.json
qapi: convert intro sections for replay.json
Quoted 15 lines
qapi/accelerator.json | 18 ++++++---------- qapi/acpi-hest.json | 4 ++-- qapi/authz.json | 21 +++++++------------ qapi/compat.json | 9 +++----- qapi/cryptodev.json | 18 ++++++---------- qapi/ebpf.json | 14 ++++++------- qapi/error.json | 3 +-- qapi/machine-common.json | 19 +++++++---------- qapi/misc-arm.json | 24 +++++++++------------ qapi/replay.json | 45 ++++++++++++++++++---------------------- qapi/trace.json | 12 ++++------- qapi/uefi.json | 5 ++--- qapi/vfio.json | 19 ++++++++--------- qapi/yank.json | 28 ++++++++++--------------- 14 files changed, 94 insertions(+), 145 deletions(-)
Why is this thread CCing linux-edac?
I don't see any relation here...
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteQuoted 41 lines · Borislav Petkov
Quoted 24 lines · John Snow
GitLab CI: https://gitlab.com/jsnow/qemu/-/pipelines/2638342206
Hi, this patchset converts some of the most trivial modules to use the new explicit intro syntax. This particular patchset does not differentiate between "trivial" conversions and those that take slightly more liberty in refactoring, but there are (debatably?) no such cases in this patchset.
John Snow (14):
qapi: convert intro sections for error.json
qapi: convert intro sections for acpi-hest.json
qapi: convert intro sections for ebpf.json
qapi: convert intro sections for uefi.json
qapi: convert intro sections for compat.json
qapi: convert intro sections for vfio.json
qapi: convert intro sections for trace.json
qapi: convert intro sections for misc-arm.json
qapi: convert intro sections for cryptodev.json
qapi: convert intro sections for machine-common.json
qapi: convert intro sections for accelerator.json
qapi: convert intro sections for authz.json
qapi: convert intro sections for yank.json
qapi: convert intro sections for replay.jsonQuoted 15 lines
qapi/accelerator.json | 18 ++++++---------- qapi/acpi-hest.json | 4 ++-- qapi/authz.json | 21 +++++++------------ qapi/compat.json | 9 +++----- qapi/cryptodev.json | 18 ++++++---------- qapi/ebpf.json | 14 ++++++------- qapi/error.json | 3 +-- qapi/machine-common.json | 19 +++++++---------- qapi/misc-arm.json | 24 +++++++++------------ qapi/replay.json | 45 ++++++++++++++++++---------------------- qapi/trace.json | 12 ++++------- qapi/uefi.json | 5 ++--- qapi/vfio.json | 19 ++++++++--------- qapi/yank.json | 28 ++++++++++--------------- 14 files changed, 94 insertions(+), 145 deletions(-)
Quoted 3 lines
Why is this thread CCing linux-edac?
I don't see any relation here...
The linux-edac list was recently added to the QEMU MAINTAINERS file:
https://gitlab.com/qemu-project/qemu/-/commit/4c5e70b9a42744401fc10b17cc61820586ba4a13
and the entry matches the qapi/acpi-hest.json file that John has modified, so gets auto-CC'd.
Admittedly the content in this series is not especially relevant to the liunux-edac list in this case, but the patch submission tools are just following the declared MAINTAINERS file entry.
With regards,
Daniel
Signature · 3 lines
|: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
Borislav Petkov
maintainerQuoted 7 lines · Daniel P. Berrangé
Quoted 3 lines
Why is this thread CCing linux-edac?
I don't see any relation here...
The linux-edac list was recently added to the QEMU
MAINTAINERSfile:
Quoted 8 lines
https://gitlab.com/qemu-project/qemu/-/commit/4c5e70b9a42744401fc10b17cc61820586ba4a13
and the entry matches the
qapi/acpi-hest.jsonfile that John has modified, so gets auto-CC'd.Admittedly the content in this series is not especially relevant to the liunux-edac list in this case, but the patch submission tools are just following the declared
MAINTAINERSfile entry.
Thanks for letting me know.
@Mauro, please remove a linux-kernel mailing list from being CCed with qemu patches. This is only going to cause a huuuge confusion as it is already showing.
Please do a separate list only for qemu RAS stuff.
Thx.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteBorislav Petkov
maintainerPATCH 1/1 MAINTAINERS: Remove linux-edac
Quoted 17 lines · Borislav Petkov
Quoted 7 lines · Daniel P. Berrangé
Quoted 3 lines
Why is this thread CCing linux-edac?
I don't see any relation here...
The linux-edac list was recently added to the QEMU
MAINTAINERSfile:Quoted 8 lines
https://gitlab.com/qemu-project/qemu/-/commit/4c5e70b9a42744401fc10b17cc61820586ba4a13
and the entry matches the
qapi/acpi-hest.jsonfile that John has modified, so gets auto-CC'd.Admittedly the content in this series is not especially relevant to the liunux-edac list in this case, but the patch submission tools are just following the declared
MAINTAINERSfile entry.
Quoted 7 lines
Thanks for letting me know.
@Mauro, please remove a linux-kernel mailing list from being CCed with qemu patches. This is only going to cause a huuuge confusion as it is already showing.
Please do a separate list only for qemu RAS stuff.
---
From: "Borislav Petkov (AMD)" <[email protected]>
Date: Fri, 3 Jul 2026 08:19:53 -0700
Subject: [PATCH] MAINTAINERS: Remove linux-edac
The commit
4c5e70b9a427 ("MAINTAINERS: update HEST maintainership entries")
added a linux kernel mailing list (linux-edac) which gets CCed automatically with qemu patches. This is absolutely confusing and it should not happen. Qemu should have its own ras mailing list where stuff like that goes.
Drop that list.
--- MAINTAINERS | 1 - 1 file changed, 1 deletion(-)
MAINTAINERS +0 -1
@@ -2274,7 +2274,6 @@ F: docs/devel/testing/acpi-bits.rst ACPI/HEST/GHES M: Mauro Carvalho Chehab <[email protected]> -L: [email protected] L: [email protected] S: Maintained F: hw/acpi/ghes.c
Signature · 7 lines
2.53.0
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH] MAINTAINERS: Remove linux-edac
Hi Boris,
Quoted 18 lines · On Fri, 3 Jul 2026 08:25:29 -0700 Borislav Petkov <[email protected]> wrote:
Quoted 17 lines · Borislav Petkov
Quoted 15 lines · Daniel P. Berrangé
Quoted 3 lines
Why is this thread CCing linux-edac?
I don't see any relation here...
The linux-edac list was recently added to the QEMU
MAINTAINERSfile:https://gitlab.com/qemu-project/qemu/-/commit/4c5e70b9a42744401fc10b17cc61820586ba4a13
and the entry matches the
qapi/acpi-hest.jsonfile that John has modified, so gets auto-CC'd.Admittedly the content in this series is not especially relevant to the liunux-edac list in this case, but the patch submission tools are just following the declared
MAINTAINERSfile entry.
Quoted 5 lines
Quoted 5 lines
Thanks for letting me know.
@Mauro, please remove a linux-kernel mailing list from being CCed with qemu patches. This is only going to cause a huuuge confusion as it is already showing.
I was in vacations, so I only noticed this patch today.
We use linux-edac for userspace at least since Rasdaemon beginning, so it was never a kernel-only ML. What happened in practice on the recent times is that rasdaemon patches are usually pushed as PR requests at github. Yet, still today, it is recommended to also submit them to linux-edac ML:
https://github.com/mchehab/rasdaemon#submitting-patches
Yet, I agree that having a separate ML for userspace RAS tools makes sense. I'll check on a separate thread if we can create one such list at vger.
Quoted 2 lines
Quoted 2 lines
Please do a separate list only for qemu RAS stuff.
Instead of adding a patch removing it, better to wait for the ML creation and then apply a QEMU patch changing it, and another one to rasdaemon.
Regards,
Mauro
Quoted 31 lines
---
From: "Borislav Petkov (AMD)" <[email protected]>
Date: Fri, 3 Jul 2026 08:19:53 -0700
Subject: [PATCH]MAINTAINERS: Remove linux-edacThe commit
4c5e70b9a427("MAINTAINERS: update HEST maintainership entries")added a linux kernel mailing list (linux-edac) which gets CCed automatically with qemu patches. This is absolutely confusing and it should not happen. Qemu should have its own ras mailing list where stuff like that goes.
Drop that list.
Cc Mauro Carvalho Chehab <[email protected]>Cc Markus Armbruster <[email protected]>Cc Philippe Mathieu-Daudé <[email protected]>Signed-off-by Borislav Petkov (AMD) <[email protected]>--- MAINTAINERS | 1 - 1 file changed, 1 deletion(-)MAINTAINERS +0
-0
MAINTAINERS F: docs/devel/testing/acpi-bits.rst · line 2279
Quoted 7 lines
MAINTAINERS +0
-1@@ -2274,7 +2274,6 @@ F: docs/devel/testing/acpi-bits.rst ACPI/HEST/GHES M: Mauro Carvalho Chehab <[email protected]> -L: [email protected] L: [email protected] S: Maintained F: hw/acpi/ghes.c
Thanks,
Mauro
Quoted 7 lines · John Snow
GitLab CI: https://gitlab.com/jsnow/qemu/-/pipelines/2638342206
Hi, this patchset converts some of the most trivial modules to use the new explicit intro syntax. This particular patchset does not differentiate between "trivial" conversions and those that take slightly more liberty in refactoring, but there are (debatably?) no such cases in this patchset.
Looks entirely mechanical to me. Am I missing anything?
Quoted 5 lines · Markus Armbruster
Quoted 2 lines · John Snow
GitLab CI: https://gitlab.com/jsnow/qemu/-/pipelines/2638342206
Quoted 7 lines
Quoted 5 lines
Hi, this patchset converts some of the most trivial modules to use the new explicit intro syntax. This particular patchset does not differentiate between "trivial" conversions and those that take slightly more liberty in refactoring, but there are (debatably?) no such cases in this patchset.
Looks entirely mechanical to me. Am I missing anything?
Honest answer: I am not sure; I have edited so many QAPI files that I cannot remember what is and what is not mechanical anymore. If there are instances of "non-mechanical" changes, it would be for cases where I decide to indent some paragraphs, but not others, effectively introducing a new split as to what appears before and what appears after the tabular data.
I genuinely do not recall if there are any such cases in this mini-series.
Quoted 14 lines · John Snow
Quoted 5 lines · Markus Armbruster
Quoted 2 lines · John Snow
GitLab CI: https://gitlab.com/jsnow/qemu/-/pipelines/2638342206
Quoted 7 lines
Quoted 5 lines
Hi, this patchset converts some of the most trivial modules to use the new explicit intro syntax. This particular patchset does not differentiate between "trivial" conversions and those that take slightly more liberty in refactoring, but there are (debatably?) no such cases in this patchset.
Looks entirely mechanical to me. Am I missing anything?
Quoted 8 lines
Honest answer: I am not sure; I have edited so many QAPI files that I cannot remember what is and what is not mechanical anymore. If there are instances of "non-mechanical" changes, it would be for cases where I decide to indent some paragraphs, but not others, effectively introducing a new split as to what appears before and what appears after the tabular data.
I genuinely do not recall if there are any such cases in this mini-series.
It's only mostly mechanical.
Almost always, the patches change
##
# @name:
#
# Single plain paragraph: Lorem ipsum dolor sit amet ut enim ad minim
# veniam duis aute irure dolor. # # Something other than a plain paragraph
to
##
# @name:
# Single plain paragraph: Lorem ipsum dolor sit amet ut enim ad
# minim veniam duis aute irure dolor.
#
# Something other than a plain paragraph
No decisions, thus mechanical.
I found two exceptions:
1. In qapi/compat.json
@@ -39,8 +37,7 @@
##
# @CompatPolicy:
-#
-# Policy for handling deprecated management interfaces.
+# Policy for handling deprecated management interfaces.
#
# This is intended for testing users of the management interfaces.
#
# Limitation: covers only syntactic aspects of QMP, i.e. stuff tagged
# with feature 'deprecated' or 'unstable'. We may want to extend it
# to cover semantic aspects and CLI.
#
# Limitation: deprecated-output policy @hide is not implemented for
# enumeration values. They behave the same as with policy @accept.
#
# @deprecated-input: how to handle deprecated input (default 'accept')
#
# @deprecated-output: how to handle deprecated output (default
# 'accept')
#
# @unstable-input: how to handle unstable input (default 'accept')
# (since 6.2)
#
# @unstable-output: how to handle unstable output (default 'accept')
# (since 6.2)
#
# Since: 6.0
##Here, we have multiple paragraphs, and only the first one becomes "intro".
2. In qapi/misc-arm.json
@@ -29,9 +28,8 @@
##
# @query-gic-capabilities:
-#
-# It will return a list of `GICCapability` objects that describe its
-# capability bits.
+# It will return a list of `GICCapability` objects that describe
+# its capability bits.
#
# On non-ARM targets this command will report an error as the GIC
# technology is not applicable.
#
# Since: 2.6
#
# .. qmp-example::
#
# -> { "execute": "query-gic-capabilities" }
# <- { "return": [{ "version": 2, "emulated": true, "kernel": false },
# { "version": 3, "emulated": false, "kernel": true } ] }
##Here, we have two paragraphs, and both become "intro".