From: nifan.cxl@gmail.com
To: mcgrof@kernel.org
Cc: nmtadam.samsung@gmail.com, kdevops@lists.linux.dev,
jlayton@kernel.org, a.manzanares@samsung.com,
Fan Ni <nifan.cxl@gmail.com>
Subject: [PATCH 0/4] CXL: add test workflow for dynamic capacity device
Date: Tue, 28 Nov 2023 14:42:00 -0800 [thread overview]
Message-ID: <20231128224331.324500-1-nifan.cxl@gmail.com> (raw)
From: Fan Ni <nifan.cxl@gmail.com>
The patch series add test workflow for CXL dynamic capacity
device (DCD) in Qemu.
Patch 1: add new options in kconfig to enable qmp interface for qemu so qemu
can be launched with qmp interface enabled, which is needed for CXL test like
error injection, dynamic capacity extent add/release.
Patch 2: add a new cxl topology where a DCD device is directly attached to the
root port of a host bridge. For the device itself, it has no static volatile
or non-volatile capacity but only dynamic regions with no DC extents added yet.
Path 3: add a new make command "cxl-create-dc-region" to create DC
region for dynamic capacity, which is needed before dc extents can be
added. We also fixed "make cxl" command as the regular cxl-mem-setup
worklfow does not work for dcd device.
Patch 4: add a new make command "cxl-dcd-setup" to add dc extents, and
convert dynamic capacity to system ram and online it.
With the patch series, we can play with DCD device in two ways,
First workflow:
After system bringup, run "make cxl" which will create DC region, create dax
device and convert it to system ram.
The other workflow:
After system bringup, and if ndctl is already available in the guest,
perform the following two steps:
1) make cxl-create-dc-region: create a DC region;
2) make cxl-dcd-setup: add dc extents, create dax device and convert it to
system ram.
Fan Ni (4):
qemu: Add QMP connection option for QMP interface access
CXL: Add a new topology to support DCD device emulation
CXL: Add new make command to create DC region for DCD device
CXL: Setup DCD device as onlined system memory
playbooks/roles/cxl/defaults/main.yml | 2 +
.../cxl/tasks/cxl-create-dc-region/main.yml | 27 +++++++
.../roles/cxl/tasks/cxl-dcd-setup/main.yml | 79 +++++++++++++++++++
playbooks/roles/cxl/tasks/main.yml | 16 ++++
playbooks/roles/gen_nodes/defaults/main.yml | 4 +
.../roles/gen_nodes/templates/Vagrantfile.j2 | 19 ++++-
scripts/gen-nodes.Makefile | 12 +++
vagrant/Kconfig | 23 ++++++
workflows/cxl/Makefile | 19 ++++-
9 files changed, 197 insertions(+), 4 deletions(-)
create mode 100644 playbooks/roles/cxl/tasks/cxl-create-dc-region/main.yml
create mode 100644 playbooks/roles/cxl/tasks/cxl-dcd-setup/main.yml
--
2.42.0
next reply other threads:[~2023-11-28 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 22:42 nifan.cxl [this message]
2023-11-28 22:42 ` [PATCH 1/4] qemu: Add QMP connection option for QMP interface access nifan.cxl
2023-11-28 22:42 ` [PATCH 2/4] CXL: Add a new topology to support DCD device emulation nifan.cxl
2023-11-28 22:42 ` [PATCH 3/4] CXL: Add new make command to create DC region for DCD device nifan.cxl
2023-11-28 22:42 ` [PATCH 4/4] CXL: Setup DCD device as onlined system memory nifan.cxl
2023-12-05 6:21 ` [PATCH 0/4] CXL: add test workflow for dynamic capacity device Luis Chamberlain
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=20231128224331.324500-1-nifan.cxl@gmail.com \
--to=nifan.cxl@gmail.com \
--cc=a.manzanares@samsung.com \
--cc=jlayton@kernel.org \
--cc=kdevops@lists.linux.dev \
--cc=mcgrof@kernel.org \
--cc=nmtadam.samsung@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).