From: Chen Pei <cp0613@linux.alibaba.com>
To: Alistair Francis <alistair23@gmail.com>
Cc: jic23@kernel.org, pbonzini@redhat.com, palmer@dabbelt.com,
alistair.francis@wdc.com, liwei1518@gmail.com,
daniel.barboza@oss.qualcomm.com, zhiwei_liu@linux.alibaba.com,
chao.liu.zevorn@gmail.com, sunilvl@ventanamicro.com,
dave.jiang@intel.com, alison.schofield@intel.com,
imammedo@redhat.com, mst@redhat.com, guoren@kernel.org,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
linux-cxl@vger.kernel.org
Subject: Re: [PATCH v2 2/4] hw/riscv/virt-acpi-build: Add _DEP to ACPI0017 for CXL host bridge dependency
Date: Tue, 7 Jul 2026 19:50:20 +0800 [thread overview]
Message-ID: <20260707115030.5161-1-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <CAKmqyKNmFdJRUegowCGggk+4fOmY7vBxOH+_gnmTSpNhyqWqHg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 983 bytes --]
Hi Alistair,
On Mon, 6 Jul 2026 14:08:45 +1000, Alistair Francis wrote:
> What happens to kernels that don't have this change?
Good question. The behavior depends on how old the kernel is:
- Kernels that support _DEP processing but lack the
acpi_dev_clear_dependencies() call in acpi_pci_root_add(): the
ACPI0017 (CXLM) device will remain deferred indefinitely because
its declared dependency on ACPI0016 is never cleared. CXL memory
would be unusable on such kernels with this QEMU.
- Very old kernels that ignore _DEP entirely: the behavior is the
same as v1 — the probe-ordering race between acpi_pci_root and
cxl_acpi remains, but nothing is worse than before.
The kernel-side fix has already merged:
https://lore.kernel.org/linux-pci/20260526025118.38935-1-cp0613@linux.alibaba.com/
So this is effectively a "new QEMU requires a sufficiently new kernel
for CXL to work" situation, similar to other QEMU features that depend
on kernel support.
Thanks,
Pei
next prev parent reply other threads:[~2026-07-07 11:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 9:38 [PATCH v2 0/4] hw/riscv/virt: Add CXL support to the RISC-V virt machine Chen Pei
2026-06-18 9:38 ` [PATCH v2 1/4] " Chen Pei
2026-06-24 16:42 ` Daniel Henrique Barboza
2026-06-29 9:06 ` Chen Pei
2026-06-18 9:38 ` [PATCH v2 2/4] hw/riscv/virt-acpi-build: Add _DEP to ACPI0017 for CXL host bridge dependency Chen Pei
2026-07-06 4:08 ` Alistair Francis
2026-07-07 11:50 ` Chen Pei [this message]
2026-07-09 3:56 ` Alistair Francis
2026-06-18 9:38 ` [PATCH v2 3/4] hw/riscv/virt,gpex: Provide 32-bit MMIO window for CXL host bridges Chen Pei
2026-06-24 17:21 ` Daniel Henrique Barboza
2026-06-29 9:10 ` Chen Pei
2026-06-18 9:38 ` [PATCH v2 4/4] tests/qtest: Add RISC-V ACPI bios tables test for CXL Chen Pei
2026-07-06 4:10 ` Alistair Francis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260707115030.5161-1-cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=alison.schofield@intel.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=chao.liu.zevorn@gmail.com \
--cc=daniel.barboza@oss.qualcomm.com \
--cc=dave.jiang@intel.com \
--cc=guoren@kernel.org \
--cc=imammedo@redhat.com \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=liwei1518@gmail.com \
--cc=mst@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sunilvl@ventanamicro.com \
--cc=zhiwei_liu@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox