From: Raghu H <raghuhack78@gmail.com>
To: maverickk1778@gmail.com, Jonathan.Cameron@huawei.com,
qemu-devel@nongnu.org
Cc: Raghu H <raghuhack78@gmail.com>
Subject: [PATCH v1 0/2] Update CXL documentation
Date: Thu, 6 Apr 2023 18:58:37 +0530 [thread overview]
Message-ID: <20230406132839.3357195-1-raghuhack78@gmail.com> (raw)
In-Reply-To: <20230406113640.0000277c@Huawei.com>
Thanks Jonathan for quick review/comments on earlier patch, as suggested
splitting into two separate patches
https://www.mail-archive.com/qemu-devel@nongnu.org/msg952999.html
Removed the unsupported size option for cxl-type3 device, Qemu reads
the device size directly from the backend memory device config.
Currently the Qemu CXL emulation for AARCH64 is not available and its
only supported on x86_64 platform emulations. Removing the incorrect
information and populating with supported x86_64 sample command to
emulate cxl devices.
The document will be updated when the AARCH64 support is mainlined.
Raghu H (2):
docs/cxl: Remove incorrect CXL type 3 size parameter
docs/cxl: Replace unsupported AARCH64 with x86_64
docs/system/devices/cxl.rst | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
base-commit: 7d0334e49111787ae19fbc8d29ff6e7347f0605e
--
2.34.1
next prev parent reply other threads:[~2023-04-06 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 10:27 [PATCH] docs:remove cxl3 device size Raghu H
2023-04-06 10:36 ` Jonathan Cameron via
2023-04-06 13:13 ` [PATCH v1 0/2] Update CXL documentation Raghu H
2023-04-06 13:13 ` [PATCH v1 1/2] docs/cxl: Remove incorrect CXL type 3 size parameter Raghu H
2023-04-06 13:13 ` [PATCH v1 2/2] docs/cxl: Replace unsupported AARCH64 with x86_64 Raghu H
2023-04-06 13:28 ` Raghu H [this message]
2023-04-06 13:28 ` [PATCH v2 1/2] docs/cxl: Remove incorrect CXL type 3 size parameter Raghu H
2023-04-06 13:28 ` [PATCH v2 2/2] docs/cxl: Replace unsupported AARCH64 with x86_64 Raghu H
2023-04-13 9:28 ` [PATCH v1 0/2] Update CXL documentation Jonathan Cameron via
2023-04-14 11:34 ` RAGHU H
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=20230406132839.3357195-1-raghuhack78@gmail.com \
--to=raghuhack78@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=maverickk1778@gmail.com \
--cc=qemu-devel@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 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 NNTP newsgroup(s).