I recently checked qom introspection for dangling child and link
types, and found one from sgx-epc to memory-backend-epc.  I reported

    Subject: qemu-system-x86_64 appears to have sgx-epc, but not 
memory-backend-epc
    Date: Thu, 22 Oct 2026 14:58:16 +0200
    Message-ID: <[email protected]>

Daniel identified why: we register QOM type "memory-backend-epc"
conditionally.  He called that "rather dubious".  We found similar
conditional registration of "hostmem-memfd".

This series makes them both unconditional, along with a two class
properties.  It also improves error reporting.

Markus Armbruster (7):
  backends/hostmem: Drop redundant validation of property "size"
  backends/hostmem-file: Drop useless validation of property "mem-path"
  backends/hostmem: Improve error reporting when method alloc() fails
  backends/hostmem-epc: Register QOM type unconditionally
  backends/hostmem-memfd: Register QOM type unconditionally
  util/memfd: Improve error message when memfd_create() fails
  backends/hostmem-memfd: Add huge TLB properties unconditionally

 backends/hostmem-epc.c   | 12 +-----------
 backends/hostmem-file.c  |  9 ---------
 backends/hostmem-memfd.c | 35 +++++++++++++----------------------
 backends/hostmem-ram.c   |  5 -----
 backends/hostmem-shm.c   |  7 +------
 backends/hostmem.c       |  3 +++
 util/memfd.c             |  5 ++++-
 7 files changed, 22 insertions(+), 54 deletions(-)

-- 
2.55.0


Reply via email to