All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yuquan Wang" <wangyuquan1236@phytium.com.cn>
To: jonathan.cameron <Jonathan.Cameron@Huawei.com>
Cc: qemu-arm <qemu-arm@nongnu.org>
Subject: CXL Namespaces of ACPI disappearing in Qemu demo
Date: Thu, 10 Aug 2023 17:30:43 +0800	[thread overview]
Message-ID: <2023081017304217150830@phytium.com.cn> (raw)
In-Reply-To: 20230619105809.000007b9@Huawei.com

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

Hi, Jonathan

When I tested the CXL topology in qemu, I found the linux kernel could find 
and match the ACPI0016&ACPI0017 in relevant drivers, however, I could not 
find these information in dumped ACPI tables (like DSDT). 

Hence, I guess there is some problem in my method, maybe you have some 
suggestions if you have some time to look at this email.

My environment:
qemu: Jonathan_qemu/cxl-2023-08-07
Linux: v6.3.0
ACPI Disassembler: iasl/version 20230628

My qemu script is the same as the first example in qemu/docs/system/devices/cxl.rst, 
as below:
  qemu-system-x86_64 -M q35,cxl=on -m 4G,maxmem=8G,slots=8 -smp 4 \
  ...
  -object memory-backend-file,id=cxl-mem1,share=on,mem-path=/tmp/cxltest.raw,size=256M \
  -object memory-backend-file,id=cxl-lsa1,share=on,mem-path=/tmp/lsa.raw,size=256M \
  -device pxb-cxl,bus_nr=12,bus=pcie.0,id=cxl.1 \
  -device cxl-rp,port=0,bus=cxl.1,id=root_port13,chassis=0,slot=2 \
  -device cxl-type3,bus=root_port13,persistent-memdev=cxl-mem1,lsa=cxl-lsa1,id=cxl-pmem0 \
  -M cxl-fmw.0.targets.0=cxl.1,cxl-fmw.0.size=4G


Many thanks
Yuquan

[-- Attachment #2: Type: text/html, Size: 2378 bytes --]

  reply	other threads:[~2023-08-10  9:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16  7:43 A confusion about CXL in arm virt machine Yuquan Wang
2023-06-16 18:10 ` Gregory Price
2023-06-19  9:58   ` Jonathan Cameron via
2023-06-19  9:58     ` Jonathan Cameron via
2023-08-10  9:30     ` Yuquan Wang [this message]
2023-08-10 10:04       ` CXL Namespaces of ACPI disappearing in Qemu demo Jonathan Cameron via
2023-08-10 13:56         ` Jonathan Cameron via
2023-08-11 10:31           ` Yuquan Wang
2023-08-22 15:23             ` Jonathan Cameron via
2023-08-22 15:23               ` Jonathan Cameron via
2023-09-18 12:41     ` A confusion about CXL in arm virt machine Peter Maydell
2023-09-18 15:03       ` Jonathan Cameron via
2023-09-18 15:03         ` Jonathan Cameron via
  -- strict thread matches above, loose matches on Subject: below --
2023-08-22  7:22 CXL Namespaces of ACPI disappearing in Qemu demo Yuquan Wang
2023-08-23 19:44 ` Gregory Price
2023-08-24  1:11   ` Yuquan Wang
2023-08-24  9:06   ` Jonathan Cameron via
2023-09-04 10:27     ` Yuquan Wang
2023-09-04 12:43       ` Jonathan Cameron via
2023-09-04 12:43         ` Jonathan Cameron via
2023-09-05 10:45         ` Yuquan Wang
2023-09-05 14:34           ` Jonathan Cameron via
2023-09-05 14:34             ` Jonathan Cameron via
2023-09-06 11:22             ` Yuquan Wang
2023-09-07 10:58               ` Jonathan Cameron via
2023-09-07 10:58                 ` Jonathan Cameron via

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=2023081017304217150830@phytium.com.cn \
    --to=wangyuquan1236@phytium.com.cn \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=qemu-arm@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.